I'm [EMAIL PROTECTED] logs now and seeing absolutely nothing that might indicate what the problem is. Unless I actually check from another account to make sure I'm not online everything would appear to be working perfectly; I just wouldn't be receiving responses from people.
When I first installed PyAIM-t it worked great for a couple of days, but as I used it more I started noticing occasionally that the roster wouldn't be updated with people who I knew to be online, [EMAIL PROTECTED] same time I wouldn't get responses from people who should have been around. With the C transport we had a problem in that AOL would disconnect people with lots of users. It turned out that the transport would seek out the away message of every away user, which would hit AOL's rate cealing. Since the transport didn't actually do anything when it received rate warnings it basically committed suicide. Could that be happening here? Is there code in this transport that seeks the status information for every user in rapid fire? Where is this code? ~Chris On Fri, 14 Jan 2005, Daniel Henninger wrote: > 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 >> > > > _______________________________________________ > py-transports mailing list > [EMAIL PROTECTED] > http://mail.jabber.org/mailman/listinfo/py-transports > From [EMAIL PROTECTED] Fri Jan 14 12:00:24 2005 From: [EMAIL PROTECTED] (Chris Carlin) Date: Fri Jan 14 12:00:24 2005 Subject: [py-transports] AIM Stability In-Reply-To: <[EMAIL PROTECTED]> References: <[EMAIL PROTECTED]> <[EMAIL PROTECTED]> Message-ID: <[EMAIL PROTECTED]> Ok, here's what I've found. There's evidence that I was right in my suspicions that AOL was disconnecting due to breaking the rate limiting. Basically, as soon as PyAIM-t completes the sign on process, Psi seems to request info on every user signed on [EMAIL PROTECTED] PyAIM-t dutifully passes these requests on to AOL, which triggers the disconnect. Unfortunately I don't think twister considers [EMAIL PROTECTED], and so there's no really good solution to this problem. The Right Way to fix it would be to back off on transmission whenever AOL tells us to. My quick and dirty hack was to do a sleep(random()*30) to spread the away message requests over the course of thirty seconds. It keeps me online, but... Anyway, so this is a bug (well, deficiency) in twister, and it will bite anyone with a large buddy list with lots of people online when they try to sign on. ~Chris On Fri, 14 Jan 2005, Daniel Henninger wrote: > 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 >> > > > _______________________________________________ > py-transports mailing list > [EMAIL PROTECTED] > http://mail.jabber.org/mailman/listinfo/py-transports > From [EMAIL PROTECTED] Fri Jan 14 12:05:25 2005 From: [EMAIL PROTECTED] (Daniel Henninger) Date: Fri Jan 14 12:05:25 2005 Subject: [py-transports] AIM Stability In-Reply-To: <[EMAIL PROTECTED]> References: <[EMAIL PROTECTED]> <[EMAIL PROTECTED]> <[EMAIL PROTECTED]> Message-ID: <[EMAIL PROTECTED]> Yikes. =/ I'll see if I can figure out a way to make twisted do what AOL wants it do to. Or.. come up with something else to fix the issue. ;) If you haven't already, would you mind submitting a jabberstudio bug report? Daniel -- "The most addictive drug in the world is music." - The Lost Boyz > Ok, here's what I've found. > > There's evidence that I was right in my suspicions that AOL was > disconnecting due to breaking the rate limiting. Basically, as soon as > PyAIM-t completes the sign on process, Psi seems to request info on every > user signed on [EMAIL PROTECTED] PyAIM-t dutifully passes these requests on to > AOL, which triggers the disconnect. > > Unfortunately I don't think twister considers [EMAIL PROTECTED], and so > there's no really good solution to this problem. The Right Way to fix it > would be to back off on transmission whenever AOL tells us to. My quick > and dirty hack was to do a sleep(random()*30) to spread the away message > requests over the course of thirty seconds. It keeps me online, but... > > Anyway, so this is a bug (well, deficiency) in twister, and it will bite > anyone with a large buddy list with lots of people online when they try to > sign on. > > ~Chris > > On Fri, 14 Jan 2005, Daniel Henninger wrote: > >> 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 >>> >> >> >> _______________________________________________ >> py-transports mailing list >> [EMAIL PROTECTED] >> http://mail.jabber.org/mailman/listinfo/py-transports >> > _______________________________________________ > py-transports mailing list > [EMAIL PROTECTED] > http://mail.jabber.org/mailman/listinfo/py-transports >
