Stuart Donaldson [mailto:stuartd@...] wrote:
> Given that some things work a little different between NT/Unix,
> can you put a quick test in and see if the catch KeyboardInterrupt
> is ever getting called, and let me know?
I just tried it. Looks like KeyboardInterrupt never gets raised (on
windows). It's the signal that causes the shutdown to be called.
> I can incorporate some cleanup into my subclassable
> ThreadedAppServer patch.
> Part of which will make it so experiments like Ian's
> could be done through subclassing, rather than
> re-implementation. That way
> the NT/Unix differences can be kept in as few places as
> possible. (I am
> aware that the NewThreadedAppServer also cleans up some stuff in
> ThreadedAppServer so it is a little more than just a new
> paradigm for the
> socket handling...)
Would it be better to make your modifications to NewThreadedAppServer rather
than to ThreadedAppServer? It may save time down the road if
NewThreadedAppServer becomes the standard.