- From: Andy Seaborne <andy@apache.org>
- Date: Sat, 05 Oct 2013 17:48:35 +0100
- To: public-rsp@w3.org
On the web, and indeed in any system of more than modest size and in one
management domain, issues of
* out of order delivery, including arbitrarily late arrival
* new stream producers coming online, old stream producers ending
(discovery, joining, leaving)
* consumers joining and leaving
* streams becoming unavailable
* ... then restarting (with or without loss of potential events)
leading to design points on
+ choice of timestamps
+ delivery ordering semantics
+ delivery guarantees (at least once, exactly once, at most once)
+ persistence, and for how long
(forwards, for guaranteed delivery and backwards for consumers to
catch up).
What are your thoughts on these issues? In-scope or out-of-scope of the
CG? Necessary or optimal to consider?
Andy
Received on Saturday, 5 October 2013 16:49:07 UTC