<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type">
</head>
<body bgcolor="#ffffff" text="#000000">
Hi,<br>
<br>
Jason Johnson wrote:
<blockquote
cite="mid:aa22f0200710251103k2e0292b4l8805478e4e5c80f4@mail.gmail.com"
type="cite">
<pre wrap="">On 10/25/07, Peter William Lount <a class="moz-txt-link-rfc2396E" href="mailto:peter@smalltalk.org"><peter@smalltalk.org></a> wrote:
</pre>
<blockquote type="cite">
<pre wrap=""> The "process-based model of concurrency" - as used in Erlang - is but one
approach in a wide range of techniques that provide solutions for
concurrency.
</pre>
</blockquote>
<pre wrap=""><!---->
A wide range? I'm aware of variations of only 3 ideas.</pre>
</blockquote>
<br>
What are they?<br>
<br>
<br>
<blockquote
cite="mid:aa22f0200710251103k2e0292b4l8805478e4e5c80f4@mail.gmail.com"
type="cite">
<pre wrap=""> Could you expand on "wide range"?
</pre>
</blockquote>
<br>
Sure, one only has to search the internet for "concurrency" and one
sees a wide range of problems and potential solutions. Look at the
Little Book of Semaphores for a breathtaking look at a few of the many
possible solutions to various problems. Open your eyes to the wider
horizon.<br>
<br>
<br>
<br>
<blockquote
cite="mid:aa22f0200710251103k2e0292b4l8805478e4e5c80f4@mail.gmail.com"
type="cite">
<pre wrap="">
</pre>
<blockquote type="cite">
<pre wrap="">It doesn't solve every problem in concurrency - I don't even
think that they claim that for it. If they do please show us where.
</pre>
</blockquote>
<pre wrap=""><!---->
Would you please stop making a statement that I obviously didn't say
(you even quoted me!) and then attacking that statement you made as
though it were mine? I find that quite disingenuous.
</pre>
</blockquote>
<br>
I never said you stated that explicitly - I'd have to check all your
postings to find that out. It's implied by what you are saying in many
of your postings. At least that is the impression that I'm getting from
your writing. You've certainly not acknowledged the opposite. <br>
<br>
<br>
<blockquote
cite="mid:aa22f0200710251103k2e0292b4l8805478e4e5c80f4@mail.gmail.com"
type="cite">
<blockquote type="cite">
<pre wrap=""> Further the example of the one million object graph being processed by
10,000 compute nodes processing the problem is that you don't know in
advance how to slice up the data. If you can know in advance how to slice up
the data then you've simplified and possibly optimized the problem solving.
However, that's the problem, slicing up real world data object sets that are
highly interconnected with each other and processing them in parallel.
That's an example of a more general case. There are other examples that
won't compute with the slice em and dice em approach using the process-based
model of concurrency.
</pre>
</blockquote>
<pre wrap=""><!---->
Do you have any real-world cases where it's a problem? I'm not
interested in solving theoretical problems that never come up in
actual practice.</pre>
</blockquote>
<br>
<br>
Yes, the example I gave is a good summary of real world problems that
actually occur (and that I'm working to solve for one project). It's
not just theory, it's a harsh reality.<br>
<br>
<br>
<br>
Cheers,<br>
<br>
Peter<br>
<br>
<br>
</body>
</html>