On Fri, Jun 17, 2005 at 12:02:43AM -0400, Bob Wyman wrote: > BTW: I think the "best" way to implement the application you describe is > probably via a combination of Push and Pull. If you're updating as rapidly > as you say you are, then it would make sense to push the updates to the > client using something like "Atom over XMPP"[1]. You would, however, still > generate Atom files and serve them using RFC3229+feed. The Atom files would > be used by clients to "catch up" on missed messages when they initially > connect or reconnect to the push stream after having been off-line for some > time. > The hybrid Push+Pull process described above is what we implement at > PubSub for every subscription. We currently have this implemented in our > PubSub Sidebars for IE and Firefox[2]. Also, the Gush reader from 2entwine > implements this hybrid Push+Pull approach when reading our feeds. > Push+Pull with Atom and Atom over XMPP gives you the best of both > worlds. You get very efficient and low latency publishing of new entries to > clients as well as efficient downloading of "catchup" files. What more > could you want? :-) > > bob wyman > > [1] http://www.xmpp.org/drafts/draft-saintandre-atompub-notify-02.html
I see that I-D is due to expire on July 15. I'll review it this week to bring it up to date with the latest Atom protocol I-D. Peter -- Peter Saint-Andre Jabber Software Foundation http://www.jabber.org/people/stpeter.shtml
