I think its interesting to point out that some code detects this and others doesn't.
In my above example, client #2 eventually sees client #1 online when the next presence tag is sent to the server. And it works if client #2 comes on first, then client #1 My psi (client #2) and my roster building code all are in lower case. On Mon, Jun 1, 2009 at 5:16 PM, Alex Vandiver <ale...@bestpractical.com> wrote: > On Mon, 2009-06-01 at 17:07 -0700, Martin Atkins wrote: >> No, that was not addressed. I don't think there was consensus on how >> best to handle backward compatibility. >> >> I'm happy to merge it if I'm mistaken and there was some consensus on this. > > I've not seen anyone actually complain about backwards compatability. > But my most recent patchset includes both conversion tools to upgrade > those who are being silently bitten by this, as well as a flag which can > be enabled to preserve the current broken behavior, if they so choose. > I don't recall anyone being explicitly dissatisfied with the those > options for dealing with the backcompat issue. > - Alex > >