Re: [Caml-list] Smart ways to implement worker threads

2010-07-16 Thread Rich Neswold
On Fri, Jul 16, 2010 at 8:02 AM, Goswin von Brederlow wrote: > Yeah. But then why not build it around the simple Mutex and Condition > modules instead of Event? At first glance the blocking aspect of Events > seem to be more of a hindrance than help. > The problem with Mutex and Condition is all

[Caml-list] Re: Smart ways to implement worker threads

2010-07-16 Thread Dawid Toton
> I find it odd that there is no Threaded_Queue module, a thread save > version of Queue with 2 extra functions: (...) > I use such a thread-safe queue a lot [1]. This is very simple yet universal enough. Honestly I can hardly remember using more elaborate constructs. Dawid [1] http://pfpleia

Re: [Caml-list] Smart ways to implement worker threads

2010-07-16 Thread Romain Beauxis
Le vendredi 16 juillet 2010 08:05:10, vous avez écrit : > > Now, the main thread does not need to be a task.. > > But then how does the main thread notice when a checksum is finished > computing? The information has to flow both ways. I would say its implemented in the replay_request function. Y

Re: [Caml-list] Smart ways to implement worker threads

2010-07-16 Thread Goswin von Brederlow
Romain Beauxis writes: > Le jeudi 15 juillet 2010 22:52:53, Goswin von Brederlow a écrit : >> The main task will only process priority 0 events and bounce between >> main_task and with_checksum while the worker threads process priority 1 >> events and do_checksum. >> >> Correct? > > I think it s

Re: [Caml-list] Smart ways to implement worker threads

2010-07-16 Thread Goswin von Brederlow
Rich Neswold writes: > On Thu, Jul 15, 2010 at 11:02 PM, Goswin von Brederlow > wrote: > > Rich Neswold writes: > > Thanks. That is about what I got so I do seem to understand the > differences right. > > For my use case this would then come down to implement solution 3 with >