Hi Philip!
Philip Shepherd wrote:
Before you are sending the <presence/> packet, send an individual
presence to the transports that shows you as offline (<presence
to='transport.domain.com' type='unavailable'/>).
I've not yet been able to get this to work properly. Sending the
"unavailable"
presence to a transport layer, does cause the the layer to logout. However,
global presence messages are still received by the transport layer, so as
soon as I send a global presence message, the transport layer logs back in.
AFAIK this shouldn't happen. The session manager should keep track of
individual presences and not use the default presence for them.
This behaviour seems to be dependent on the way the Jabber server processes
individual presence messages. i.e. We would get the desired effect if the
Jabber
server did not send global presence messages to jid's which have already
received
an individual presence message.
If you know of a Jabber server with which this tactic is known to work,
please
send me the details so I can resolve this issue on my own Jabber server.
The session manager of jabberd 1.4.x should work this way.
Tot kijk
Matthias
--
Fon: +49-(0)70 0770 07770 http://matthias-wimmer.de/
Fax: +49-(0)89-312 88 654 jabber:[EMAIL PROTECTED]
HAM: DB1MW
_______________________________________________
jdev mailing list
[EMAIL PROTECTED]
http://mailman.jabber.org/listinfo/jdev
