Comments on: Binary Data is XMPP’s Achilles Heel

By: Thoughts On Scalable XMPP Bots « metajack

Thoughts On Scalable XMPP Bots « metajack — Mon, 04 Aug 2008 17:25:55 +0000

[...] a large roster means an enormous stanza in the connection startup. As I’ve written before, large stanzas are bad. Pretty much all processing will stop for the bot while it receives and deals with this stanza. [...]

By: metajack

metajack — Tue, 10 Jun 2008 22:37:28 +0000

@peter: Wait until you see our new project! I can tell you it mixes HTTP and XMPP quite nicely

By: Peter Saint-Andre

Peter Saint-Andre — Tue, 10 Jun 2008 22:18:05 +0000

Hmm, XMPP + HTTP would result in a kind of hybrid technology, and anything hybrid is red hot right now. I see some marketing possibilities…

By: metajack

metajack — Tue, 10 Jun 2008 18:40:52 +0000

@peter: Yes of course. Perhaps I should have made this clearer in the article. It was implied when I talked about large messages. Hybrid use of HTTP works great as a workaround, but is a little cumbersome for many applications. Also it requires a little finessing to work across server boundaries. There would need to be a stream:features for telling clients where the HTTP service is for avatars for example. So perhaps in addition to extending the XEPs for in-band bytestreams, we also should create an out of band HTTP service extension as well.

By: Peter Saint-Andre

Peter Saint-Andre — Tue, 10 Jun 2008 17:25:35 +0000

It’s not just binary data, it’s large data (some big SVG or DocBook file would cause just as many problems). And yes we need to figure this out, perhaps by encouraging more hybrid usage of XMPP and HTTP.