[jdev] Multiplexing large number of client connections
jonathan at dickinsons.co.za
Mon Jan 25 17:41:32 CST 2010
There is definitely interest on my side. I will basically have a single client that other processes connect to via IPC - the cleanest solution would be resources, although the client could always open up new connections. In any case it would be great for scenarios like mine (basically delegation).
Sorry for not conforming to the list standards, I am on my mobile.
From: Peter Saint-Andre <stpeter at stpeter.im>
Sent: 25 January 2010 11:40 PM
To: Jabber/XMPP software development list <jdev at jabber.org>
Subject: Re: [jdev] Multiplexing large number of client connections
On 1/25/10 2:29 PM, Tomasz Sterna wrote:
> Dnia 2010-01-24, nie o godzinie 20:55 -0700, Peter Saint-Andre pisze:
>> And we removed the protocol for multiple resources over a single
>> from draft-ietf-xmpp-3920bis because list consensus led me to think
>> people believe it is unnecessary and too complicated.
> Why the hell did I spent time implementing it in jabberd2 then?
Because you are a good person and a true innovator.
The multi-resource stuff seemed like a good idea at the time but people
on the XMPP WG discussion list were concerned about adding complexity.
We could, of course, still define it as an XMPP extension if there's
More information about the JDev