I'm finding that PyAIM-t just won't stay connected for extended periods of
time. In fact,@the moment it signs off immediately after signing on.
None of this is conveyed to the user, though. As far as a user of the
transport can tell he's still online and everything's fine.
I've taken to keeping a copy of Gaim running signed on to a different
account just to see when I'm actually online and not.
Is this a known issue? Becuase it's obviously a fairly serious flaw...
~Chris
From [EMAIL PROTECTED] Fri Jan 14 10:33:56 2005
From: [EMAIL PROTECTED] (Daniel Henninger)
Date: Fri Jan 14 10:33:56 2005
Subject: [py-transports] AIM Stability
In-Reply-To: <[EMAIL PROTECTED]>
References: <[EMAIL PROTECTED]>
Message-ID: <[EMAIL PROTECTED]>
Odd, I've never had these problems. I also have been made aware of folk
who are running this transport live for a while now and haven't had any
problems like this. (the not alerting users is definitely a problem I
need to address though, right now PyAIM-t is mighty silent about problems,
except in the logs) Typically folk with misconfigured firewalls run into
this type problem, but... ?
Daniel
--
"The most addictive drug in the world is music."
- The Lost Boyz
> I'm finding that PyAIM-t just won't stay connected for extended periods of
> time. In fact,@the moment it signs off immediately after signing on.
> None of this is conveyed to the user, though. As far as a user of the
> transport can tell he's still online and everything's fine.
>
> I've taken to keeping a copy of Gaim running signed on to a different
> account just to see when I'm actually online and not.
>
> Is this a known issue? Becuase it's obviously a fairly serious flaw...
>
> ~Chris
> _______________________________________________
> py-transports mailing list
> [EMAIL PROTECTED]
> http://mail.jabber.org/mailman/listinfo/py-transports
>
