I am working on a patch to integrate much of the functionality of the ThreadedAppServer.run() function into a method on ThreadedAppServer so it can be more easily subclassed.
In trying to not break any existing functionality, I have a couple of questions: The run function currently catches KeyboardInterrupt exceptions. However signals for this are also caught and directed to the shutDown function. Is there a case where the KeyboardInterrupt exceptions would get thrown? Would it make more sense if, after returning from mainloop() we checked to see if we were still running, and then called shufDown() if needed? Also, the NT code never seems to call shutDown(), it just sets server.running=0. Is this a problem on NT? I don't have much NT/Python combined experience so I don't know why it might not want to call shutDown() and cleanup the queues. Stuart Donaldson ------------------------------------------------------- This sf.net email is sponsored by: With Great Power, Comes Great Responsibility Learn to use your power at OSDN's High Performance Computing Channel http://hpc.devchannel.org/ _______________________________________________ Webware-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/webware-devel