Getting concurrency

[Sean Hinde]

>
> For threads-and-locks, one could start with a big lock
> and successively refine it, e.g., split the critical
> region into smaller ones and try to shrink them, etc.
> Doing this might not yield an optimal solution, but it
> would at least optimize execution a bit.
>
> Is there a useful equivalent to this for message
> passing?

One process for each real world concurrent activity?

>
> OK, back to work ... :-)

Good to hear it ;-)

Sean