On 12/26/06, Magnus Henoch <[EMAIL PROTECTED]> wrote:
This is only half true. ejabberd has an excellent pubsub module
For the record, I totally agree with everything you said, I've just seen how hard it it to implement stuff server/transport/component side, and client side with a moving target/spec. With some pubsub use cases finally being worked out (eg: PEP), there will be a chance to actually implement some code server & client side, that does user appreciable stuff (that's what sells MSNMSGR right?) You wouldn't need a full pubsub server for rss, you _could_ simulate the pubsub nodes, and populate them directly from the rss feeds - it does mean you can't re-use the code which sucks, you also can't spread the load, and/or aggregate multiple feed checkers onto a single pubsub component. I chatted briefly with the PyMSNt author about adding PEP support for avatars, and by the sounds of it he thought it was a lot of work (i.e. implementing _all_ the pubsub use cases), but if all you're doing is avatars, then you only really need update notifications - subscriptions, etc are moot, because they now follow presence subscriptions. (hrm, I may add PEP avatars to PyYIMt to confirm this) FYI: I really like the way rss.jabber.ru works at the moment: I can create my own feeds, and subscribe to existing feeds. New messages are delivered as 'headline' events. If the underlying protocol was changed to pubsub+atom/rss/rdf (as long as the look-and-feel stayed the same) then as a user a would be equally happy. As an XMPP developer I would be ecstatic :-) (disclaimer: I haven't tried JabRSS, so I can't compare it to rss.jabber.ru) -- - Norman Rasmussen - Email: [EMAIL PROTECTED] - Home page: http://norman.rasmussen.co.za/ _______________________________________________ py-transports mailing list [email protected] http://www.modevia.com/cgi-bin/mailman/listinfo/py-transports
