I'm remembering old conversations about this now, and the problem was that everything is just a JID and distinguishing tranports is a non trivial task (because they could be remote). So it's best to just go offline/invis and let the clients deal with it if they want to. Although that really strains the transports oddly since they kill the session and then immediately bring it back up. Maybe if the client sent the invisible to the transports first and the jabberd tracked jids that had been notified already so it wouldn't send the offlines to them. Then the transports can take the correct action without stopping and starting a remote session a lot.
--temas On Thu, 2002-07-11 at 15:45, Matthias Wimmer wrote: > Hi Thomas! > > Thomas Muldowney wrote: > > >As far as I know (and after conferring with Julian) all the transports > >currently interpret it as offline. So the users session to the remote > >network is ended. If the remote networks have hte ability, they could > >support it better in the future, but I don't think they do yet. > > > AFAIK icqv7-transport supports invisibility. The latest versions of > yahoo-transport (that don't work anymore since yesterday) supported > invisible mode too. > > The problem with it is, that the Jabber server doesn't send the > <presence type='invisible'/> packet to the transports. Invisibility and > transports only work if the Jabber client sends an addresses invisible > <presence/> to a transport. > The only clients that support this at the moment are JAJC and Gabber. I > don't know how they check which contact is a transport and if this can > be faked by a user (and therefore the user would get the invisible > presence that it shouldn't get). In my opinion the best way would be if > the server sends invisible presences to its transports. This should be > more secure then a Jabber client deciding to whilch users (that are > transports) invisible presence has to be sent. > > > Tot kijk > Matthias > > -- > Fon: +49-700 77007770 http://matthias-wimmer.de/ > Fax: +49-89 312 88654 jabber:[EMAIL PROTECTED] > > > _______________________________________________ > jdev mailing list > [EMAIL PROTECTED] > http://mailman.jabber.org/listinfo/jdev _______________________________________________ jdev mailing list [EMAIL PROTECTED] http://mailman.jabber.org/listinfo/jdev
