General wisdom on this is: delegate this task to a suborocess
(preferrably via the new multiprocessing module, or pyro), and
terminate that if it didn't return after x seconds.
You can also use ctypes to expose thread killing functions from your
OS, but that's a slippery road better not to walk down.
Diez
Am 23.04.201 um 05:17 schrieb Sam <[email protected]>:
In the administrative back end for 1000 Corks our admins can do some
complicated pattern matching. Occasionally a pattern match will be so
inefficient it seems to more or less bring cherrypy to its knees for
minutes at a time.
I'd like to have some way of timing these requests out and returning
an appropriate message.
Can I do this?
--
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?hl=en
.
--
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?hl=en.
