Benoit Tellier created JAMES-3531:
-------------------------------------
Summary: JMAP RFC-8620 SSE transport should manage Last-Event-Id
Key: JAMES-3531
URL: https://issues.apache.org/jira/browse/JAMES-3531
Project: James Server
Issue Type: Sub-task
Components: JMAP
Affects Versions: 3.6.0
Reporter: Benoit Tellier
Assignee: Antoine Duprat
According to https://jmap.io/spec-core.html#event-source
{code:java}
The server SHOULD also send a new event id that encodes the entire server state
visible to
the user immediately after sending a state event. When a new connection is made
to the
event-source endpoint, a client following the server-sent events specification
will send a
Last-Event-ID HTTP header field with the last id it saw, which the server can
use to work
out whether the client has missed some changes. If so, it SHOULD send these
changes
immediately on connection.
{code}
This is currently not implemented.
This enable re-synchronization in the face of intermittent network connection
using only SSE, without API calls.
This is somehow equivalent to RFC-8887 (JMAP over websocket) `pushState`
mechanism. See https://tools.ietf.org/html/rfc8887.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
