[JDEV] Presence bug in Jabber 0.9

David Waite mass at ufl.edu
Wed Apr 5 11:56:00 CDT 2000

Hmm, but shouldn't type="available" work anyways? just because it is the
default attribute doesn't mean it can't still be present. I thought that
elements could have different meanings based on whether they were present or
not, but the absence of an attribute defaulted it to (a predetermined) one
if its possible states.

-David Waite

-----Original Message-----
From: jdev-admin at jabber.org [mailto:jdev-admin at jabber.org]On Behalf Of
Kerem 'Waster_' HADIMLI
Sent: Wednesday, April 05, 2000 11:50 AM
To: jdev at jabber.org
Subject: Re: [JDEV] Presence bug in Jabber 0.9

you should NEVER send a type='available' in <presence> tag. If u don't send
type attribute in <presence>, then it'll mean that you're available. If you
send any type attribute, then it'll mean you're unavailable (please note:
always send type='unavailable' for unavailable mode, although any string in
type attribute will work).

It isn't required to send "<presence/>", if you're sending a <presence> tag
without type attribute. It's just for marking you 'available' in server.


Nickolai Kussovski wrote:
> Hi,
> I try to send some presence like:
> <presence type="available">
>      <show>chat</show>
> </presence>
> after the initial <presence/>
> The result is that I cannot see anybody's presences after that.
> Any idea?
> Thanks,
> Nike
> _______________________________________________
> jdev mailing list
> jdev at jabber.org
> http://mailman.jabber.org/listinfo/jdev

If it happens once, it's a bug.
If it happens twice, it's a feature.
If it happens more than twice, it's a design philosophy.

jdev mailing list
jdev at jabber.org

More information about the JDev mailing list