Bob Wyman wrote:
Joe Gregorio wrote:
The one thing missing from the analysis is the overhead, and
practicality, of switching protocols (HTTP to XMPP).
I'm not aware of anything that might be called "overhead." What our
clients do is, upon startup, connect to XMPP and request the list of Atom
files that they are monitoring. They then immediately fetch those files to
establish their start-of-session state. From that point on, they only listen
to XMPP since anything that would be written to the Atom files is also
written to XMPP. HTTP is only used on start-up. It's a pretty clean process.
I'm guessing Joe is talking about network administration. There's no
shortage of places that won't even let you use SSH or POP, never mind on
XMPP. It's port 80 via the proxy or nothing. This is an observation of
the current state of affairs, please don't confuse it with an advocacy
of it.
cheers
Bill
