Comments on: XMPP PubSub: a great compliment to Atom/RSS http://www.embracingchaos.com/2008/07/xmpp-pubsub-a-g.html Leo Parker Dirac on Business and Technology Trends Tue, 24 Aug 2010 02:01:59 -0700 http://wordpress.org/?v=2.9.2 hourly 1 By: Ram M. http://www.embracingchaos.com/2008/07/xmpp-pubsub-a-g.html/comment-page-1#comment-256 Ram M. Wed, 15 Jul 2009 08:26:13 +0000 http://wp.embracingchaos.com/2008/07/xmpp-pubsub-a-g.html#comment-256 <p>XMPP/PubSub as a trigger and then the actual content download through http is what I have implemented for a our internal services. The preference would be to keep the messages through xmpp servers to be smaller size, then to send the large size messages.</p> XMPP/PubSub as a trigger and then the actual content download through http is what I have implemented for a our internal services. The preference would be to keep the messages through xmpp servers to be smaller size, then to send the large size messages.

]]> By: tuttle http://www.embracingchaos.com/2008/07/xmpp-pubsub-a-g.html/comment-page-1#comment-255 tuttle Thu, 09 Jul 2009 02:27:31 +0000 http://wp.embracingchaos.com/2008/07/xmpp-pubsub-a-g.html#comment-255 <p>I really dislike this poling everywhere and I very much appreciate these efforts! But to make things easier for the beginning: why not just use XMPP/PubSub as a trigger for RSS/Atom feed updates? So all the content transport is as usual, but the client, if the feed supports it, doesn't poll anymore but waits for the "new feed entry" message on the XMPP connection. I think this is the most modular and most likely successful approach, since it is less effort to implement. In general, although capable of a lot more, XMPP/PubSub can have a success as a "trigger protocol".</p> I really dislike this poling everywhere and I very much appreciate these efforts! But to make things easier for the beginning: why not just use XMPP/PubSub as a trigger for RSS/Atom feed updates? So all the content transport is as usual, but the client, if the feed supports it, doesn't poll anymore but waits for the "new feed entry" message on the XMPP connection. I think this is the most modular and most likely successful approach, since it is less effort to implement. In general, although capable of a lot more, XMPP/PubSub can have a success as a "trigger protocol".

]]> By: Jean-Claude Mason http://www.embracingchaos.com/2008/07/xmpp-pubsub-a-g.html/comment-page-1#comment-254 Jean-Claude Mason Wed, 20 May 2009 06:23:31 +0000 http://wp.embracingchaos.com/2008/07/xmpp-pubsub-a-g.html#comment-254 <p>Great article! Just as a contribution, I found <a href="http://www.nardol.org/2009/3/18/pubsub-with-xmpp4r-simple" rel="nofollow">http://www.nardol.org/2009/3/18/pubsub-with-xmpp4r-simple</a> that eases XMPP and PubSub.</p> Great article! Just as a contribution, I found http://www.nardol.org/2009/3/18/pubsub-with-xmpp4r-simple that eases XMPP and PubSub.

]]> By: Matt Terenzio http://www.embracingchaos.com/2008/07/xmpp-pubsub-a-g.html/comment-page-1#comment-253 Matt Terenzio Thu, 07 Aug 2008 13:12:53 +0000 http://wp.embracingchaos.com/2008/07/xmpp-pubsub-a-g.html#comment-253 <p>But yes, Fritzy, there are so many invalid RSS feeds out there that it is problematic to parse as XML.</p> But yes, Fritzy, there are so many invalid RSS feeds out there that it is problematic to parse as XML.

]]> By: Matt Terenzio http://www.embracingchaos.com/2008/07/xmpp-pubsub-a-g.html/comment-page-1#comment-252 Matt Terenzio Thu, 07 Aug 2008 13:10:11 +0000 http://wp.embracingchaos.com/2008/07/xmpp-pubsub-a-g.html#comment-252 <p>RSS may not be as well-crafted as ATOM but it is XML, or should be.<br /> And it may well be that HTML and RSS are more widely adopted because of their imperfections and not in spite of them.<br /> </p> RSS may not be as well-crafted as ATOM but it is XML, or should be.
And it may well be that HTML and RSS are more widely adopted because of their imperfections and not in spite of them.

]]> By: leodirac http://www.embracingchaos.com/2008/07/xmpp-pubsub-a-g.html/comment-page-1#comment-251 leodirac Tue, 29 Jul 2008 17:18:49 +0000 http://wp.embracingchaos.com/2008/07/xmpp-pubsub-a-g.html#comment-251 <p>RSS doesn't need to be well-formed XML? Really?</p> <p>Woah. I *hate* RSS. Atom rules!</p> RSS doesn't need to be well-formed XML? Really?

Woah. I *hate* RSS. Atom rules!

]]> By: Fritzy http://www.embracingchaos.com/2008/07/xmpp-pubsub-a-g.html/comment-page-1#comment-250 Fritzy Tue, 29 Jul 2008 14:37:14 +0000 http://wp.embracingchaos.com/2008/07/xmpp-pubsub-a-g.html#comment-250 <p>RSS is to Atom as HTML is to XHTML. In short, RSS, while based on XML, isn't XML. You can't reliably parse it as XML, and thus it's not as convenient of a payload in XMPP as Atom.</p> RSS is to Atom as HTML is to XHTML. In short, RSS, while based on XML, isn't XML. You can't reliably parse it as XML, and thus it's not as convenient of a payload in XMPP as Atom.

]]> By: Peter Saint-Andre http://www.embracingchaos.com/2008/07/xmpp-pubsub-a-g.html/comment-page-1#comment-249 Peter Saint-Andre Tue, 29 Jul 2008 13:47:41 +0000 http://wp.embracingchaos.com/2008/07/xmpp-pubsub-a-g.html#comment-249 <p>Thanks for the helpful post. I think we can do the sequence numbers via SHIM headers (XEP-0131). And it would be good to standardize the link rels. Perhaps that belongs in XEP-0240? We also need to standardize the ad-hoc command (XEP-0050) for getting a node of yours to subscribe to another node for lightweight chaining or repeaters. Then I think we're most of the way there. :)</p> Thanks for the helpful post. I think we can do the sequence numbers via SHIM headers (XEP-0131). And it would be good to standardize the link rels. Perhaps that belongs in XEP-0240? We also need to standardize the ad-hoc command (XEP-0050) for getting a node of yours to subscribe to another node for lightweight chaining or repeaters. Then I think we're most of the way there. :)

]]>