Jonathan LaCour wrote: > There are not really any fundamental throughput problems in asyncore or > asynchat that I know of, other than the fact that they are a little hard > to use at first. I suspect that you were putting long-running > operations > inside your event loop, slowing down your I/O.
That was exactly the case > An approach that often works well for me is to allow asyncore to do all > of its work inside its own thread, and queue up the long-running tasks > into a Queue and process them from a separate thread. This works great > for me, and still keeps things relatively simple. Indeed, I later realised this could have been a good approach, but I couldn't really bothered to implement it all again when I know that preforking was a viable and stable solution Thanks for your advice though, if I get another project to do in this vain I'll try and get away with writing a library for this. Cheers -Rob --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "TurboGears" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/turbogears -~----------~----~----~----~------~----~------~--~---
