RE: Let's fix THE PROBLEM

(Whoops... apparently failed to send this to the list originally.)

Bob Wyman said:
>>I'm not sure how that's a single, monolithic package.
> 	Sorry. Bad word choice. A better word might be "stand-alone." In
> XMPP, Presence doesn't use either PubSub or an events package like in
SIP/SIMPLE. This may tend to result in people overloading Presence to
accomplish things that would be better done with PubSub since Presence
is almost guaranteed to be implemented by everyone whereas PubSub, as an
optional protocol extension, is now and probably will remain less
commonly implemented.

Bob-

The point of the JEP process is to build protocol extensions that will be
widely used. While it is true that there is no reason that a developer
would HAVE to use the PubSub protocol defined in JEP-0060 [1], it is
unlikely that their enhancement would be widely embraced by the Jabber
commuinity, or the JSF, if it did not use PubSub when it should have. I
agree that a generic PubSub protocol is beneficial, but one that bridges
the obvious protocol differences of XMPP and SIP/SIMPLE may be a pipe
dream.

That being said, there is certainly nothing preventing PubSub from being
brought into the IETF process. While I doubt that will happen right now, I
(and I bet others) can see value in having an IETF standardized protocol
for PubSub over XMPP. The fact of the matter is, the XMPP WG is doing its
best to get XMPP done, and standardized, and other extensions built on top
of XMPP can certainly be taken through the same process, in the future
(much like many other IETF protocols). As an example of the JSF's
dedication to correctly using PubSub protocols, when appropriate, please
refer to JEP-0084 [2], "User Avatars in Jabber."

Cheers,

bs.

1) http://www.jabber.org/jeps/jep-0060.html
2) http://www.jabber.org/jeps/jep-0084.html



  [reminder: [email protected] for non-technical discussions, please]