A served Redis frame: the payload bytes past the frame header plus the
header's creation time. The payload is the serializer output, possibly
still wrapped in a compression envelope that DialCache core interprets
above the adapter (see the dialcache/redis-protocol module doc). All
frames carry application-clock time supplied by the writer. Caller-serving
reads apply their logical age ceiling and reject frames dated after the
reading process's clock before deserialization; stale-on-error may retain a
raw frame between its fresh and maximum ages. Confirmation reads may retain
a frame solely for payload comparison. DialCache also uses createdAtMs for
shadow and stale-recovery value-age observability. Tracked watermark fencing
already happened inside the decoder.
A served Redis frame: the payload bytes past the frame header plus the header's creation time. The payload is the serializer output, possibly still wrapped in a compression envelope that DialCache core interprets above the adapter (see the
dialcache/redis-protocolmodule doc). All frames carry application-clock time supplied by the writer. Caller-serving reads apply their logical age ceiling and reject frames dated after the reading process's clock before deserialization; stale-on-error may retain a raw frame between its fresh and maximum ages. Confirmation reads may retain a frame solely for payload comparison. DialCache also usescreatedAtMsfor shadow and stale-recovery value-age observability. Tracked watermark fencing already happened inside the decoder.