thanks for your reply, actually yes i have read the part about the Be smart about timer, but this is the first time i have to manage so many timers, and something is not clear to me.
#4 refers to making a linked list and putting all timers in there but how can i control individually each timer, even though they all will have the same time out not all of them will be used the same quantity of times, each timer will have a socket associated to it, so some timers will be updated more times than others and others will expire more times than others depending on the activity in the sockets, others may not even time out at all, depending on the usage of the socket. are you aware of an example somewhere that uses timer using technique #4 ? i m sure i m missing something. thanks!!! On 2 June 2011 17:37, Marc Lehmann <[email protected]> wrote: > On Thu, Jun 02, 2011 at 04:59:22PM -0600, Juan Pablo L < > [email protected]> wrote: > > Any tip would be appreciated on how to deal with this situation, maybe > > You claim to have read the documentation but managed to miss the "Be smart > about timeouts" section? > > > i may have thousands if not millions of sockets and timers (one timer per > > socket) > > If your timeouts are all constant, then method #4 would be O(1) and very > fast, too. > > If any questions are left after reading the docs, feel free to ask them :) > > -- > The choice of a Deliantra, the free code+content MORPG > -----==- _GNU_ http://www.deliantra.net > ----==-- _ generation > ---==---(_)__ __ ____ __ Marc Lehmann > --==---/ / _ \/ // /\ \/ / [email protected] > -=====/_/_//_/\_,_/ /_/\_\ >
_______________________________________________ libev mailing list [email protected] http://lists.schmorp.de/cgi-bin/mailman/listinfo/libev
