Thanks a lot, looked into that, so it is basically a background thread performing all delayed stuff. Thinking here: maybe it would make sense to add something like onTimer handler - a user function to call every second or so. Then I could do all my TTL processing there.. Thoughts?
Mike -----Original Message----- From: [email protected] [mailto:[email protected]] On Behalf Of Nicolas Cannasse Sent: Saturday, February 13, 2010 1:48 PM To: Neko intermediate language mailing list Subject: Re: [Neko] TTL for tora.Share Michael Pliskin a écrit : > Hi Nicolas, > > Thanks for the pointer, I didn't know that. > > As for tora.api.call, I could probably use it. Is it an expensive thing? I.e. > if I would be making 10000 requests to make my socket expire in an hour and > queue them all, would that be bad? Check the implementation (Tora.speedDelayLoop for delayed events and ModToraApi.tora_call for request). Yes, handling a lot of requests should be expensive since the delayQueue is not sorted, and also because each event will cause an actual request to be processed by your service, although no network IO is done. Nicolas -- Neko : One VM to run them all (http://nekovm.org)
-- Neko : One VM to run them all (http://nekovm.org)
