Threading Model and Parallelization Model inside Movitz

--===============0875807904==
Content-Type: multipart/alternative; boundary=00221532cb882d886d046c2dfdf6

--00221532cb882d886d046c2dfdf6
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit

I was wondering if the threading.lisp file inside the losp/ directory
represents base threading model that Movitz is planning on supporting...
Also, is there an overarching design already in the works or is this an area
that still needs to be worked on?

Ram

--00221532cb882d886d046c2dfdf6
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

I was wondering if the threading.lisp file inside the losp/ directory repre=
sents base threading model that Movitz is planning on supporting... Also, i=
s there an overarching design already in the works or is this an area that =
still needs to be worked on?<br>
<br>Ram<br>

--00221532cb882d886d046c2dfdf6--


--===============0875807904==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline