Sure.
A friend had his custom presence message set to a string containing a single
quote as in " I'm not available" on GoogleTalk. It is a pretty widespread
service and all the GoogleTalk users who have such a customized string will
not have it changed, or their client upgraded overnight, which means that a
gloox-based client will have a hard time with those users for quite some
time.
Jakob, I am not saying that you are not correct from a strict protocol point
of view, but you can see how this particular gloox behavior in the face of
such an error would negatively affect gloox for a while. ;-) The real
world is full of compromises that work-around other people's bugs for just
that kind of widespread interoperability problem.
Thanks,
Philippe
_____
From: Matthew Wild [mailto:mwild1@xxxxxxxxx]
Sent: Wednesday, July 18, 2007 5:52 PM
To: gloox-dev@xxxxxxxxxx
Subject: Re: [gloox-dev] gloox 0.9.3
On 7/18/07, Philippe Roger <philippe@xxxxxxxxxxxxx> wrote:
A more balanced handling would be to simply ignore the syntax error,
possibly replacing the problematic field with an empty one, instead.
In fact a better solution would be to find out what client your contact is
using and what server they are connected to, and file bugs in the relevant
places.
Also, post the details of what you find back to this list, so other people
can be aware of it too.
Matthew.