[Openid-specs-risc] Proposal: Resync request in SSE

[Atul Tulshibagwale]

Hi all,
I'd like to discuss the possibility of a SSE Receiver going out of sync
with its Transmitter. There should be a way that the Receiver can request
to re-synchronize (resync) its state with the Transmitter. Of course, not
all Transmitters will be capable of such resyncs, so this should be an
optional functionality. Even where a Transmitter is capable of resyncing,
it may not be able to service all resync requests. The resync request may
be limited to certain event types and to certain subjects.

To capture this requirement, I'd like to propose the following *optional*
addition to the SSE Event Management API to achieve this. Please provide
your feedback, or we can discuss in the next call:

---

*Resync Request*
A Receiver MAY request a Transmitter that it needs to get updates for a
past time period, by calling the following API method:

POST /sse/stream:resync

This method has the following parameters:

   1. from_time - OPTIONAL the time from which the resync is requested. If
   this parameter is not specified, then the from_time is assumed to be from
   the time the Transmitter started the stream with the Receiver
   2. to_time - OPTIONAL the time until which the resync is requested. If
   this parameter is not specified, then the to_time is assumed to be the time
   at which the request was received
   3. events_requested - OPTIONAL the list of events that are requested to
   be resynced. If this parameter is missing, then the request is assumed to
   be for all supported events
   4. subject - OPTIONAL the subject for which the events are requested to
   be resynced. If this parameter is missing, then the request is assumed to
   be for all subjects

A Transmitter MAY provide updates to the Receiver with the assumption that
the Receiver has not processed any previously sent events during this time
period for the specified event types and for the specified subject.

---




Atul Tulshibagwale

Software Engineer,

Google Workspace

atultulshi at google.com
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openid.net/pipermail/openid-specs-risc/attachments/20210305/5edbdf1f/attachment.html>