Difference between revisions of "Real Time Web"
m (1 revision imported) |
(No difference)
|
Latest revision as of 22:48, 15 May 2015
Facilitated by Rabble and Seth
This session talked about the real time web
=
RealTimeWeb
Seth & Rabble & (Ayman).
XMPP from 7 years ago added a conversation platform WITH a data payload.
HTTP Stuff:
We are a collection of realtime APIs. So we should reverse that. RSS allowed polling. Web servers can tell you nothing changed, but the thundering heard of ppl at scale makes it overwhelming.
At the point of millions, it doesnt work. So we need an event driven model. IM isnt well supported by tools, but purely with the web, using a webserver would be easier.
Digital TV and HD radio are real time technologies: ambient information comes with the stream.
Web of Data: objects get pushed around like a Rube Goldberg machine.
Your location is interesting only if you arent there right now?
OK, so how can we share these social objects when they happen, opposed to constantly checking if something happened.
Photos are uploaded to Flickr sometimes months after they were taken.
Data is quarantined sometimes, so even then its not-so-realtime.
Old stuff:
1. RSS Clouds: It tells you when to poll again.
2. WebHooks: It tells you the changed content, but the same kinda deal?
3. PubSubHubBub: Subscription model (webhooks standarization)
4. HTTPStreams: open a connection and hold it forever.
XMPP/JABBER:
Instead of web, we go over IM and create a parallel world.
1. longstanding connections
2. trunking (from telephony)
3. buddy lists
4. peer to peer
Is the JABBER connection more robust than the HTTPStream?
Where does the infrastructure for sharing real time data with social permissions come in?
Stuff like OpenID and Oauth allow for trusted interactions.
http://www.flickr.com/explore/panda
with real time Indexes change. relevance changes.
wordpress does pubsub and xmpp.
pubsub is only useful for public data...privacy requires xmpp or running a private hub.
xep60?
websockets? html5?
Google Wave is a good connection of HTTP and XMPP for real time systems.
Wave has its own DIFFing protocol via an XML format (Rabble says more complicated).
People building have to decide whats useful and what doesnt make sense. Like my missspelling of what went wrong. (but do we need an explicit commit)
The conversation has gone from 'just a replacement for polling' to 'what can we do that will make the new experience'.