[JDEV] Re: [Gabber] probs w/ aim-t

[Julian Missig]

On 10 Jan 2001 09:17:16 -0500, Brian Lalor wrote:
> I'm running the latest released version of the aim transport (0.85?) with
> Jabber 1.2 and Gabber 0.8.  Occasionally, I'll see "AIM Transport is now
> offline", but the aimtrans process remains running.  Probably just a poor
> connection to the AIM server.
> 
> My first problem is that if the aim-t has gone offline, I can't (with
> Gabber) just log back into the transport; I have to exit the client and
> log back in.  This seems to be a problem with the aim-t not receiving the
> list of buddies it is supposed to be watching for.  If I use the Gabber
> "Log into transport" option, I will be once again connected with the AIM
> server, but I can't see the presence of my AIM buddies.

Log into transport sends a presence directly to aim-t, as it should be
doing. aim-t, however, does not remember your buddy list and gets it
when you first log in and send a presence. Supposedly, sending a
<presence/> will make the server re-send presence to everyone so aim-t
can rebuild the buddy list. In practice, however, the server does not do
this. The only time the server sends presence to everyone, including
offline users, is when you first log in. Even if you send just
<presence/> - you can try it with Help -> Debug -> Raw XML Input - it
won't work as temas says.

The result: brandon is hacking gabber to solve this with a cheap hack.
Gabber will look through the roster and find all users on that transport
and send specific presence to each of them. This increases the amount of
refreshes in the roster and stuff like that... but talking to jer, it
doesn't seem there's another way other than fixing aim-t.


> 
> The second problem I'm seeing is that if the AIM transport goes offline,
> AIM buddies in my roster don't change their presence to away.

Gabber CVS has been hacked in a similar fashion as was described above
to make all users of the transport appear offline when a transport goes
offline. Yeah, it's a hack.


> 
> Is anyone else having these problems?  I think the second problem is
> solely to do with aim-t, but I think the first is a bit more complex.
> 


Yes, I am :)

Julian

-- 
email: julian at jabber.org
jabber:julian at jabber.org