Greetings, I currently run a Twisted application that provides AIM connectivity. A while back I caught that you folks were maintaining the OSCAR protocol independently (which is awesome, thank you). I had been maintaining my own local version, as well. The main differences are ones focused on stability. I've added a variety try/excepts that are errors I've discovered via extensive use and logging. Perhaps your project would be interested in that aspect of my code.
My real intent in email is to frown on the 0.8 release which incorporates a scheduler. This scheduler uses several independent threads to defer tasks, but we are using Twisted. Why are you not using a callLater approach instead of time.sleep!? In my application, the number of threads grows too large and I am unable to create new threads for everyone due to some limit (I've not investigated this limit). I fear that I will have to maintain a local version. I've rewrote the "QueueThread" class to not actually be a thread, but rather a callLater-based queue. If you are interested in that, I can provide this code to you. -Scott -- Scott Dial [EMAIL PROTECTED] [EMAIL PROTECTED] _______________________________________________ py-transports mailing list [email protected] http://lists.modevia.com/cgi-bin/mailman/listinfo/py-transports
