in reply to Parrot, threads & fears for the future.
I've finished a first pass through PDD 25 on threading/concurrency. It's largely a collection of prior thinking on the subject. Before I start kicking it into a more structured form, I'd like to do an initial round of discussion. This is your chance to mention anything you hoped or expected from Parrot's concurrency models. How do you plan to use concurrency, and in what contexts? What's your favorite concurrency model and why should we consider using it? How integral a role should the new STM play in Parrot's concurrency? Etc.
I've changed the name of the PDD from "Threads" to "Concurrency" because: a) the notion of "threads" seems to have taken on mythical proportions, so this is a symbolic step toward practicality, and b) Parrot has more than one concurrency model, and this PDD will be the overview of all them, plus the ways the various models interact.
I intend to point her to this thread in case she does not already know about it.Cheers - L~R
|
|---|
| Replies are listed 'Best First'. | |
|---|---|
|
Re^2: Parrot, threads & fears for the future.
by BrowserUk (Patriarch) on Oct 31, 2006 at 01:03 UTC | |
by Limbic~Region (Chancellor) on Oct 31, 2006 at 13:26 UTC | |
by particle (Vicar) on Oct 31, 2006 at 14:27 UTC | |
by particle (Vicar) on Nov 16, 2006 at 17:24 UTC |