SOrry - last reply was meant for Tom!
On Wed, Aug 28, 2013 at 8:47 PM, Matthew Humphrey <mhumph...@gmail.com>wrote: > Phil - Thanks so much. This is pretty much exactly what I was looking for. > I tried the approach you suggested for timer events, and it seems very > clean and works quite well. I was able to get it working very consistently > with intervals < 10ms (way more than I need). > > I haven't tried the process management stuff yet, but it looks very > straightforward. > > Thanks again. > > > On Wed, Aug 28, 2013 at 6:54 AM, Phil Mayers <p.may...@imperial.ac.uk>wrote: > >> On 28/08/13 14:40, Tom Sheffler wrote: >> >>> >>> Hi Matthew - >>> >>> I have a couple of idioms I use for #2 and #3 in your message. Here >>> they are. >>> >>> #2) >>> >>> For timer events, I create a function that when called, continuously >>> schedules itself again in the reactor, does some work for the curren >>> >> >> Are you aware of t.i.task, specifically LoopingCall and >> cooperate/coiterate? >> >> ______________________________**_________________ >> Twisted-Python mailing list >> Twisted-Python@twistedmatrix.**com <Twisted-Python@twistedmatrix.com> >> http://twistedmatrix.com/cgi-**bin/mailman/listinfo/twisted-**python<http://twistedmatrix.com/cgi-bin/mailman/listinfo/twisted-python> >> > >
_______________________________________________ Twisted-Python mailing list Twisted-Python@twistedmatrix.com http://twistedmatrix.com/cgi-bin/mailman/listinfo/twisted-python
