On 12/26/06, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:
And just by the way, Jabber has a built in capability called pubsub or publish subscribe. It provides a way for a Jabber user to subscribe to feeds that would be published by someone or other.
Unfortunately the history behind pubsub (as I understand it), is that: - no one wants to build a pubsub/rss component/transport because no clients support pubsub yet. - no one wants to implement pubsub in a client yet, because there's no need - because no servers/transports/components implement it yet. kinda a catch 22 situation, - the full pubsub spec is also waaaaay more than any individual implementation will ever need - this is something that most people has not yet fully understood. - clients only needs 'i want to subscribe/gimme the feed/oh, here's new stuff' bits of the spec - an rss transport would only need 'okay, you're subscribed/here's the list of stuff/oh, brand new item'. a lot of the hesitation with building a pubsub component, is to do with security, access, publishing, subscribers, etc... all stuff that _most_ implementations using pubsub shouldn't even care about. -- - Norman Rasmussen - Email: [EMAIL PROTECTED] - Home page: http://norman.rasmussen.co.za/ _______________________________________________ py-transports mailing list py-transports@blathersource.org http://www.modevia.com/cgi-bin/mailman/listinfo/py-transports
