This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author jyasskin
Recipients jyasskin, phr, skip.montanaro, werneck, zanella
Date 2008-03-01.21:44:54
SpamBayes Score 0.021777695
Marked as misclassified No
Message-id <1204407897.5.0.821145170082.issue1193577@psf.upfronthosting.co.za>
In-reply-to
Content
Polling isn't a great way to handle shutdown, since it wastes CPU time
and decreases responsiveness, but it's also easy and my attempt to avoid
it isn't getting anywhere, so I'm planning to fix up your patch a bit
and commit it. Thanks!

I've merged your patch with my conflicting change in the trunk and
re-attached it.

Two things:
1) This patch may interfere with the existing timeout in await_request.
We may be able to re-use that instead of having two select statements.

2) I believe it's important to provide a way to block until the server
isn't accepting any more requests and to block until all active requests
are finished running. If the active requests depend on other bits of the
system, blocking until they're done would help them terminate
gracefully. It would also be useful to give users a more proactive way
to kill active requests, perhaps by listing the handler objects
associated with them (or their PIDs for forking servers). It's
surprisingly complicated to avoid race conditions in these
implementations, especially without support from the Server object.
History
Date User Action Args
2008-03-01 21:44:57jyasskinsetspambayes_score: 0.0217777 -> 0.021777695
recipients: + jyasskin, skip.montanaro, phr, zanella, werneck
2008-03-01 21:44:57jyasskinsetspambayes_score: 0.0217777 -> 0.0217777
messageid: <1204407897.5.0.821145170082.issue1193577@psf.upfronthosting.co.za>
2008-03-01 21:44:56jyasskinlinkissue1193577 messages
2008-03-01 21:44:55jyasskincreate