- From: Harry Halpin <hhalpin@w3.org>
- Date: Thu, 29 Jan 2015 22:33:43 +0100
- To: public-socialweb@w3.org
On 01/29/2015 10:30 PM, Evan Prodromou wrote: > Everyone is blown away by the size of these requirements already. > > A streaming protocol for streams would be a great addition later, but trying to jam it in here will literally sink this project. > > Please accept this as being out of scope. > > Evan Prodromou > >> On Jan 29, 2015, at 15:00, ☮ elf Pavlik ☮ <perpetual-tripper@wwelves.org> wrote: >> >>> On 01/29/2015 02:21 AM, Sandro Hawke wrote: >>>> On 01/28/2015 06:13 PM, Evan Prodromou wrote: >>>> >>>>> - Can you justify most of the out-of-scope stuff? Without streaming >>>>> or push, I don't see how this system could catch on. >>>> I think that server-to-server stuff is going to be more pertinent when >>>> we discuss the federation protocol. >>> >>> Clients need streaming/push, too, don't they? >> +1 >> >> in my experiments a while ago i used HTTP + JSON based pub/sub protocol >> Bayeux: http://svn.cometd.org/trunk/bayeux/bayeux.html >> >> using one of its implementations: http://faye.jcoglan.com/ >> >> mentioned decentralized prototype with real time geolocation map layers: >> https://github.com/dspace-ng/dspace-app-action-slim >> >> > Note that the W3C is also working on figuring out a consistent and standardized way to do streaming in WebApps WG [1], so quite a few APIs will be upgraded when the time comes. This applies mostly to JS APIs, not REST APIs, but may have an impact. [1] http://www.w3.org/TR/streams-api/#writableStream
Received on Thursday, 29 January 2015 21:33:52 UTC