[dmd-concurrency] priority messages

Andrei Alexandrescu andrei at erdani.com
Mon Jan 25 10:01:03 PST 2010


Steve Schveighoffer wrote:
> 
> 
> 
> ----- Original Message ----
>> From: Michel Fortin <michel.fortin at michelf.com>
>>> 2. "Must handle" messages that unblock any call to receive(). They may or may 
>> not have priority. These may be derived from Exception.
>>
>> I'd say those should be just "tasks". Sending one would execute that task in the 
>> given thread, inside receive. Tasks could be shared delegates, functions, or 
>> structs and objects defining opCall.
> 
> How does that scale to inter-process communication?  One thing that was nice about the message passing is it was seamless as far as inter-process since the messages could be serialized to be sent via IPC.  Executing arbitrary code can only be feasible within the same process.

That is correct. There will be differences between send(tid, stuff) and 
send(pid, stuff). There's stuff that you can only send across threads, 
such as shared data and (now under discussion) pointers to functions.

Andrei



More information about the dmd-concurrency mailing list