[JDEV] type='error' in presence
Julian Missig
julian at jabber.org
Sat May 11 21:53:16 CDT 2002
On Sat, 2002-05-11 at 22:43, Jim Seymour wrote:
> Justin <infiniti at affinix.com> wrote:
> >
> > On Friday 10 May 2002 13:43, Jim Seymour wrote:
> > > Julian Missig <julian at jabber.org> wrote:
> > > > Well, you treat type='error' however you want, we don't dictate that :)
> > >
> > > Well, yes, I realize *that* :). What I'm wondering is if that would
> > > be the logical thing to do? Seems like it to me.
> >
> > I don't think you need to treat it as 'unavailable', the server should take
> > care of that.
>
> One would think. But apparently it does not. Again, the presence
> message received:
>
> <presence from='buddy at jabber.myjabber.org'
> to='user at jabber.ais.cx/GAIM' type='error'>
> <status>Online</status>
> <error code='502'>Server Connect Failed</error>
> </presence>
>
Would you rather have the server tell you nothing? If type= is anything
other than 'available' then your client shouldn't be blindly assuming
it's available.
> > You might consider logging the fact that there was an error,
> > so that the user can check on it later.
>
> I'm considering what else to do other than show the "buddy" off-line.
>
> I considered doing an error pop-up, as is done with other errors. But
> if the user had a half-dozen buddies on the affected server that would
> mean a half-dozen pop-ups. No good ;).
At any given time, I probably get about 30 presence error messages each
time I connect.
>
> > Most clients probably don't do
> > anything with such presence errors though.
>
> Seems they should...
What would you recommend? Having them appear offline, or better yet, if
your client has an 'unknown' (for subscription type of 'from' or 'none')
show type seems adequate -- and if the user asks for more information
(or maybe activates the mechanism to see the 'status' message) you can
let them know there was an error in obtaining information about this
user's presence.
Julian
--
email: julian at jabber.org
jabber:julian at jabber.org
More information about the JDev
mailing list