cool, yea, this is coming off a transport that I'm trying to debug, so I've got things to attack from both ends, and it's still not working yet :-(
On 11/11/05, Peter Saint-Andre <[EMAIL PROTECTED]> wrote: > A client shouldn't receive that because a service shouldn't send it > (since initial presence would never be sent for someone whose role is > "none"). However, on the off chance that a client would receive this, I > think it should ignore it. I'm not a client developer and I don't know > how you've coded the logic, but the following makes sense to me: > > 1. Receive presence stanza from [EMAIL PROTECTED]/user > > 2. Check against room roster (is this a presence change for someone from > whom I've already received presence, or new presence for someone who's > just joined the room?) > > 3. If new and role="none" then ignore. > > Peter > > Norman Rasmussen wrote: > > Cool. > > > > So what should the client do if it receives that xml? Basically at > > the moment in the psi muc patch, I've 'fixed' it to ignore + log debug > > entry. > > > > On 11/11/05, Peter Saint-Andre <[EMAIL PROTECTED]> wrote: > >> Norman Rasmussen wrote: > >>> JEP-0045: 6.3.3 Presence Broadcast > >> <snip/> > >> > >>> with the 'role' attribute set to a value of "moderator", > >>> "participant", "visitor", or "none" > >> s/"visitor", or "none"/or "visitor"/ > >> > >> Fixed in my working copy. > >> > >> Peter > >> > > > > -- - Norman Rasmussen - Email: [EMAIL PROTECTED] - Home page: http://norman.rasmussen.co.za/
