Hi Bryan - please work with Chaals to schedule some time for this topic.
Currently, the schedule is full but it may be possible to shorten the
time allocated for a specific topic or to add it at the end of the day
i.e. 17:00:
http://www.w3.org/2008/webapps/wiki/TPAC2011#Agenda_Tuesday.2C_November_1
(FYI, I have a conflict with Web Events' f2f meeting and will not arrive
@ WebApps' meeting until 10:00.)
On 11/1/11 4:52 AM, ext Bryan Sullivan wrote:
As further input on this proposed discussion, please see the
unofficial draft of the "EventSource API Connectionless Push
Extension" at http://bkaj.net/w3c/eventsource-push.html.
Hopefully webapps will have at least 30 minutes open in the schedule
for Tuesday so I can introduce this API draft proposal, and we can
discuss the other alternatives noted below.
Comments are welcome.
Bryan Sullivan
On Mon, Oct 31, 2011 at 1:40 AM, Bryan Sullivan<[email protected]> wrote:
Hi Art and Chaals,
If possible (depending upon the Webapps agenda fullness) I would like
to propose a 30-60 minute discussion on followup work we have been
pursuing on extending Server-Sent Events for support of Connectionless
Push, as noted in the current SSE draft (the section
http://dev.w3.org/html5/eventsource/#eventsource-push, which resulted
from the last discussion we had on this in Webapps in the 2009 TPAC).
If there is time for this (at least 30 minutes) I can send info in
advance tomorrow, which will describe some approaches we have been
considering, including:
- adding support for additional URI schemes for eventsource, to
indicate additional bearers ("sources") for eventsource events
- processing of events from connectionless Push bearers (SMS, OMA
Push/SMS, and OMA Push in general) using the text/event-stream
processing model
- alternatively, using device-local eventsource server addresses as a
way to seamlessly extend eventsource for these additional bearers,
without impacting the browser
- any other ideas that Webapps members might have on how this can be
achieved with as much consistency with eventsource as possible (even
complete transparency, if possible)
This would be in essence a kickoff discussion of this in Webapps, if
the group overall thinks any of the ideas are well-formed enough to
pursue in some spec form.Otherwise the feedback would be useful
anyway, to help improve the API extension concepts and prototypes we
have been developing for submission to Webapps at the right time.
--
Thanks,
Bryan Sullivan
