Last-Event-ID
The header a Server-Sent Events client sends when reconnecting, carrying the id of the last event it received so the server can continue from there.
In more detail
The server must document whether and for how long it can replay history, and clients must tolerate receiving an event twice. The value comes from the id field of the last event the client received.
Related terms
- Server-Sent Events — A standard way for a server to keep an HTTP response open and push a stream of text events to the client, in one direction only.
- reconnection — Re-establishing a dropped long-lived connection and, where supported, resuming from the last message received.
- replay — Delivering or returning something again: a stored result for a repeated request, or past events for a client that missed them.
- EventSource — The Argo Events resource that listens to an outside source, such as a webhook or a queue, and publishes what arrives as events.
- ring buffer — A fixed-size array used as a loop: when writes reach the end they wrap to the start, overwriting the oldest data.
Taught in
- Server-Sent Events — Modern API Architecture: REST, GraphQL & gRPC
- Server-Sent Events: Streaming Updates & Recovery — Production Full-Stack Engineering