W3C home > Mailing lists > Public > public-socialweb@w3.org > January 2015

Re: on API Requirements

From: ☮ elf Pavlik ☮ <perpetual-tripper@wwelves.org>
Date: Fri, 30 Jan 2015 12:39:13 +0100
Message-ID: <54CB6D61.6070505@wwelves.org>
To: Evan Prodromou <evan@e14n.com>
CC: Sandro Hawke <sandro@w3.org>, 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 I think we make sure to keep *extensibility* in mind and design
things in a way which will make it straight forward to publish
additional spec later which will enable streaming interfaces!

In dspace-ng modules, I experimented with channels which in javascript
exposed methods channel.read() channel.write() using HTTP
GET/POST/PUT/DELETE and channel.pub() channel.sub() using realtime
messaging over websockets with Bayeux. I believe other people here also
must have some experience in this field...

@Sandro do you have by any chance, already something concrete to share
with us about streaming/push? Maybe something you've discovered working
with Andrei on http://crosscloud.org/ ? :)

Last but not least, pretty much all W3C groups use IRC heavily,
including ourselves. I see more and more people basing their
collaboration on tools like Slack, HipChat, Gitter etc. Also twitter,
facebook etc. all push data to clients in real time. I would say, more
power to everyone who wants to work on enabling real time features for
technology stack we work on here!

Received on Friday, 30 January 2015 11:39:37 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 17:26:14 UTC