> [Excerpts from last message] >> I wanted to suggest an approach to implement a similar API like >> "Twitter's streaming API": >> One could utilize SQLSpaces (available under >> http://sqlspaces.collide.info/) as a base and mediator for message >> based communication.. > > I have decided for a new approach: > One could use pubsubhubbub protocol > (http://code.google.com/p/pubsubhubbub/) to develop a plug-in for real > time streaming. This plug-in can empower Statusnet with live streaming > functionalities in following manner: > > i) it should integrate with the core and provide essential > functionalities as live stream > ii) it should make it possible for plug-ins to register "streamable" > content > iii) it should provide a layer which extends internal privacy and > authentication system in order to manage stream's privacy > > Since this protocol uses simple HTTP (and supports HTTPS), it can be > assured that this feature can be implemented platform-independent. > For regular browser based communication with the server, one could > utilize Ajax long-polling to realize a live-stream communication. > > I would really appreciate feedback > Regards > Pouyan
PubSubHubBub requires that the server and client each be able to connect to each other. It's obvious that the client (browser) can connect to the server (StatusNet), but in many (if not most) cases, the server cannot connect to the client because the client is behind NAT, a firewall, or something else. In an all IPv6 world (or the Internet of 15 years ago) this would be a good idea, but I don't know how to get around this problem with the current Internet. Do you have any thoughts? Good luck, ~Craig _______________________________________________ StatusNet-dev mailing list StatusNet-dev@lists.status.net http://lists.status.net/mailman/listinfo/statusnet-dev
