[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: OS-implemented threads



Matthew Flatt <mflatt@cs.utah.edu> writes:

> [Collecting several replies into one message.]
> 
[snip]
> 
> Quoting Alexander Taranov:
> > For the project we are working at OS-implemented threads
> > would be of great value. If it would work i would use it.
> > The project is live one and in case of using OS-threads
> > you will not complain on the lack of bug reports :-)
> 
> As much as I appreciate bug reports, I'm even more eager to avoid the
> bugs that make them necessary. :)
> 
> In your project, would OS-implemented threads be valuable due to
> blocking function calls, as in Ilya's project, or would they be
> valuable for making use of multiple processors? Or something else?

Both blocking calls in extensions and using multiple processors.
Actually I need an engine which acts as server and in each 
`server thread' extensions with blocking I/O are called.

Now we are using `slow and dirty' solution starting an instance of
mzscheme for each request.

--at


[snip]

> Matthew