I wonder if it might be best to create a "proxy" server of some sort that exposes a Twitter compatible streaming API. We would use one of the existing realtime plugins (xmpp, comet, etc) as the source of the notices.
So something like this... Client <--Streaming API---> Stream API frontend proxy <------> XMPP/Comet/etc backend server & plugin <----> StatusNet The streaming API proxy would translate the messages it receieves from xmpp/comet into JSON documents which are than streamed to the client. If the client is using any filters, it would also apply those before sending out any notices. So the existing realtime plugins / servers act as a backend to this streaming API frontend. It understands comet/xmpp and translate it into the twitter Streaming API protocol. Josh
_______________________________________________ StatusNet-dev mailing list StatusNet-dev@lists.status.net http://lists.status.net/mailman/listinfo/statusnet-dev
