Transport Presence 0.10.0.0

[GoogleCodeExporter]

What steps will reproduce the problem?
1. Subscribe to AOL, MSN, and Yahoo transports
2. Login to account, and login to transports
3.

What is the expected output? What do you see instead?
I expect to see presence in the transport icons, instead they show off line.

What version of the product are you using? On what operating system?
0.10.0.0 xp pro SP2

Please provide any additional information below.
Just upgraded from latest version that was available at old website.

Original issue reported on code.google.com by charlie....@gmail.com on 26 Nov 2007 at 5:21

[GoogleCodeExporter]

I am seeing this same issue with transport presence in version 0.10.0.0.  The 
icons
next to the MSN, Yahoo, ICQ and AIM transports are all grey.  I have seen this 
with
Vista and XP. I can log into the same Jabber server with Exodus version 0.9.1.0 
and
the icons next to the Transports are all orange.  I am attaching a .txt file 
that
contains the debug xml that I see when I register with the Yahoo transport using
Exodus version 0.10.0.0.
Also, below is some smaller pieces of xml that I see when I register with the 
Yahoo
transport using Exodus version 0.9.1.0 and 0.10.0.0.  I am posting these for
comparison between the two version of the Exodus if it helps.  Note: the JID and
jabber server name in the xml below has be change from the original.

This is the XML that I see when I register with the Yahoo transport using 
Exodus ver.
0.9.1.0

SENT: <iq id="jcl_20" to="yahoo.jabberserver.uark.edu" type="set"><query
xmlns="jabber:iq:register"><username>changed</username><password>*****</password
></query></iq>
RECV: <iq xmlns='jabber:client' to='myjabberid@jabberserver.uark.edu/Exodus'
from='yahoo.jabberserver.uark.edu' id='jcl_20' type='result'><query
xmlns='jabber:iq:register'/></iq>
RECV: <presence xmlns='jabber:client' 
to='myjabberid@jabberserver.uark.edu/Exodus'
from='yahoo.jabberserver.uark.edu' id='99' type='unavailable'/>

This is the XML that I see when I register with the Yahoo transport using 
Exodus ver.
0.10.0.0

[2008-02-19 16:51:22.495]  SENT: <iq id="jcl_36" 
to="yahoo.jabberserver.uark.edu"
type="set"><query
xmlns="jabber:iq:register"><username>changed</username><password>*******</passwo
rd></query></iq>
[2008-02-19 16:51:22.587]  RECV: <iq xmlns='jabber:client'
to='myjabberid@jabberserver.uark.edu/Exodus' from='yahoo.jabberserver.uark.edu'
id='jcl_36' type='result'><query xmlns='jabber:iq:register'/></iq>
[2008-02-19 16:51:22.808]  RECV: <presence xmlns='jabber:client'
to='myjabberid@jabberserver.uark.edu/Exodus' from='yahoo.jabberserver.uark.edu'
id='310' type='set'/>
[2008-02-19 16:51:23.014]  RECV: <presence xmlns='jabber:client'
to='myjabberid@jabberserver.uark.edu/Exodus' from='yahoo.jabberserver.uark.edu'
id='326'/>
[2008-02-19 16:51:23.024]  RECV: <presence xmlns='jabber:client'
to='myjabberid@jabberserver.uark.edu/Exodus' from='yahoo.jabberserver.uark.edu'
id='327'/>

Original comment by Les.Seig...@gmail.com on 27 Feb 2008 at 7:54

Attachments:

• Yahoo-Transport-registration-log.txt

[GoogleCodeExporter]

I see the same thing here with 0.10.0.0 xp pro SP2.  I thought this seemed 
familiar
so I looked through all my previous posts.  I found one from 3/13/2004 with 
subject
[Exodus] Transports still not working in Exodus.  I was using 0.9.0.5 then.  It 
looks
like the problem is the same as it was 4 years ago.  Peter's answer then was:

The problem is that there is no good way for clients to detect roster items as
transports. The way that Exodus currently uses is to treat all roster entries in
the "Transports" group as transports. Nothing more, nothing less. It's possible
(but sometimes annoying) to have the client auto-detect entries in the form of
"foo.com" and "foo.com/registered" as transports, but for some folks, this is
not always the case. The current behavior is correct, so if you want to add
something, add it as a Feature Request (not a bug). I suspect both Psi and
Gabber treat anything w/out a user part of the jid as a transport. This works
for some folks, but not all. (Especially for those of us that have services on
our roster, like: notes.jabber.org, or something similar).

pgm.

Is it still the same problem?

Original comment by damonreg...@bellsouth.net on 11 Apr 2008 at 12:38

[GoogleCodeExporter]

I can't say for sure if 0.10.0.0 has the same problem as 0.9.0.5.  I currently 
have
version 0.9.1.0 installed and the transports all show online in that version 
whether
they are in a group called Transports or in another group such as Unfiled.  In
version 0.10.0.0 they are currently in the Transport group and they do not all 
show
online even when they are connected. (Actually since my first post two of my
transports now show offline and two show online when they are connected).  I am 
using
the same Jabber ID on the same Jabber server.  This makes me think that 
something
changed from version 0.9.0.5 to version 0.10.0.0 but I can't say for sure.  I 
do know
that Transports presence works OK in Exodus 0.9.1.0 and in Psi and Pandion, 
etc.  so
I hope this issue will be addressed as a bug in 0.10.0.0.

Original comment by Les.Seig...@gmail.com on 18 Apr 2008 at 2:43