[JDEV] fascinating JabberIM bug.
Nathan J. Mehl
memory at blank.org
Wed Dec 27 12:27:28 CST 2000
After several days of banging my head against JabberIM, I finally
managed to isolate the case of a very strange bug.
Environment: jabberd 1.2 on RedHat 6.2. JabberIM 0.9.6.86 on Win98
and Win2000. Gabber 0.7.0 on RedHat 6.2 and 7.0.
The scenario:
Assume two users:
testuser1 at jabber.example.org
TestUser2 at jabber.example.org
testuser1 is logged in using JabberIM. It doesn't appear to matter
which client TestUser2 uses.
If TestUser2 logs in as "testuser2 at jabber.example.org", everything
works fine -- the users can exchange presence and chat with each other
normally.
BUT, if TestUser2 logs in as "TestUser2 at jabber.example.org", each
message he sends to testuser1 is interpreted by JabberIM as a "new"
message, and JabberIM opens a new window for each line sent. If
JabberIM is set to "Display only latest chat window for new messages",
the previous window is deleted. If that option is unchecked, the
windows stack up one after the other.
The _only_ determining factor here appears to be whether the currently
logged-in JID uses capital letters. The case of the registered ID
does not appear to be significant. JabberIM was the only client I
found that displayed this behavior: Gabber, WinJab and HotJabber all
behave correctly.
I would be _very_ curious to know if anybody else can reproduce this,
or if they have any insight into why it happens.
-n
------------------------------------------------------------<memory at blank.org>
Ocean water in / my small, light aircraft engine / makes me very dead.
Environmental / avaitor is that the / water there? Oh God!
Rocky mountain high / sunshine on my shoulder now / makes me decompose.
(--haikus for John Denver)
<http://www.blank.org/memory/>------------------------------------------------
More information about the JDev
mailing list