[prev in list] [next in list] [prev in thread] [next in thread] 

List:       jabber-bugs
Subject:    Re: [JBUG] Presence Bugs
From:       Jeremie <jeremie () jabber ! org>
Date:       1999-11-07 17:05:50
[Download RAW message or body]

> First, don't know what happened last night.  First I'm sitting at the computer
> awake, next thing I know I'm waking up in my bed.  WEIRD.  Anyway, I played
> with presence some this morning and here is what I've noticed.

Hehe, done that, been there :)

> 1)  The from field given to the clients is always from="jabber:jabber" this
> doesn't seem very descriptitve as to who is actually changing their presence.

Thats what mass was getting last night as well, strange, I wasn't getting
it... I'll wipe my box clean of src/libs and start over

> 2)  The presence is broadcasted to all users it seems, and not just the users
> on with roster tags.  This may be planned though (?).

Nope, that's not even possible in the source I wrote :)

BUT, what you are likely seeing is that presence is internally broadcast
to a user's own resources.  So, when you connect a second time with a new
resource on the same account, a forced <presence type="available/> is sent
to the first (or any other) resource (which they should respond to with
their presence), same when you disconnect. This is so that you are forced
to see all of your own resources that are connected.

Also, when you connect your "default" or preset presence is <presence
type="unavailable"/> which anyone gets if they poll you or if they come
online and the server replies with your presence.

Actually... hmm.. I just thought of a few more logic bugs in the presence
stuff, I'll fix this afternoon or tonight.

> 
> 3)  I still can't seem to get presence to a second user that is connected
> 
> I'll be around tonight to work on this more (pre4?).

Ditto, I'll be back on tonight to hammer on this stuff, presence is no fun
and just makes everything complicated :(

Jer



[prev in list] [next in list] [prev in thread] [next in thread]