Re: [JDEV] jabbertransport quirk?

[Jeremie <jeremie@jabber.org>]

What you're hitting here is the special multi-client mode, where one
single socket can be multiplexed for multiple logins.  As soon as the
transport notices a secondary login on the same socket, it creates another
session for that login and expects the client to start identifying each
incoming "packet" of data.  For this slightly different syntax, take a
look at: http://jabber.org/download/latest/doc/protocol/multiclient.txt

Jer

On Mon, 19 Jul 1999, Thomas D. Charron wrote:

>   Could someone please validate for me that this happens?  If you login TWICE to a transport (Aka, send two login messages), it would seem that jabbertransport gets ALL confused..  When I send this:
> 
> <message><to>u</to><from>u</from><say>HiGuy</say></message>
> 
>   After logging in twice with the same username/password, jabbertransport does this:
> 
> [Mon Jul 19 13:27:05 1999] lib "IO: waiting"
> [Mon Jul 19 13:27:05 1999] lib "new_data_from=127.0.0.1"
> [Mon Jul 19 13:27:05 1999] main "dispatch_data=<message><to>u</to><from>u</from><say>HiGuy</say></message>"
> [Mon Jul 19 13:27:05 1999] main "Processing Normally"
> [Mon Jul 19 13:27:05 1999] main "handling_normal_packet=127.0.0.1"
> [Mon Jul 19 13:27:05 1999] main "handle_message"
> [Mon Jul 19 13:27:05 1999] main "Invalid message, improper from or to"
> 
>   Now, I'm NOT condoning that that people SHOULD be logging in twice, but this could cause problems if a socket get's hung, and someone logs in a second time via a transport, but the first one hasn't disconnected yet for some reason..
> ---
> Thomas Charron
> 
> 
> --== Sent via Deja.com http://www.deja.com/ ==--
> Share what you know. Learn what you don't.
>