> -----Original Message----- > From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On > Behalf Of David Waite > Sent: Saturday, June 28, 2003 7:25 PM > To: [EMAIL PROTECTED] > Subject: Re: [JDEV] Multiple connects / AIM-t not disconnecting? > > > Steven Brown wrote: > > >It's really buggy. :( aim-t sticks to the first client that > logged in, > >and msn-t doesn't send initial presense to the second > client. It'd be > >_really_ nice to have these working, as it's blowing the > advantage of > >Jabber's resources. > > > Nobody has successfully defined 'working' yet. There are a million > edge-cases when mapping multiple sessions to a transport.
It's not that hard, at least I don't see any big problems. The transport should connect when first a user is seen from any resource, disconnect when the last resource for that user disconnects, and broadcast presence to each resource just like Jabber. When a message is received, it should be routed like a normal jabber message to the highest priority resource. I tried to fix aim-t to do this for our own use at one point, but its use of jids is inconsistent and confusing, and I eventually ran out of time and had to leave it as-is. I'm sure someone with more experience with these transports could fix them in a day if motivated. _______________________________________________ jdev mailing list [EMAIL PROTECTED] http://mailman.jabber.org/listinfo/jdev
