I indeed concur with your assessment and quite frankly think a few bits within my recent thread changes are wrong. I'm going to tidy my code up and then freeze it from any new changes for analysis on my threads. Quite simply put I'm not fully happy with how it is at the moment.
One main thing I'll also do is separate into files, it should no longer be one big file. On 25/03/2008, Romain Beauxis <[EMAIL PROTECTED]> wrote: > Le Wednesday 26 March 2008 02:39:39 Peter Brooks, vous avez écrit : > > > Ie we want to know the latest metadata & the status of the cue button > > regally, the current design on the svn creates a new thread for each > > watcher. This obviously being quite wasteful on system resources if we > > have 20 things watching and 20 threads. > > Also the current system doesn't check if it has anything new to emit, > > it just emits data no matter what. Ie If there's no changes in the > > queue it still emits a signal and bothers the liststore checkers. > > > For such a need, we recently implemented a similar thing using the "select" > call. I think it's available in python: > http://docs.python.org/lib/module-select.html > But it may not be under windows.. > > The basic for such thing is a main thread, which waits on the interesting > sockets, and perform actions when needed. And for timed events, you also have > a timeout parameter. > > That way you can map several watch processes inside a single "collaborative" > thread. > > > Romain > > -- > How can a man > Discover a land > That already populated with Indians? > > > ------------------------------------------------------------------------- > Check out the new SourceForge.net Marketplace. > It's the best place to buy or sell services for > just about anything Open Source. > http://ad.doubleclick.net/clk;164216239;13503038;w?http://sf.net/marketplace > _______________________________________________ > Savonet-devl mailing list > [email protected] > https://lists.sourceforge.net/lists/listinfo/savonet-devl > -- Peter Brooks
