[plt-scheme] Re: SOAP for PLT-scheme?

Ah, I was misinformed.  :-)  

My app needs to do three kinds of IO (a lot)  
-- socket i/o for http as a client and server: std.browser -to-
web-server - to - xml-rpc server
-- db requests to postgresql, presumably using the schematics spgsql
library, which uses the PG socket interface.
-- file i/o, mostly serving files and writing logs. 

I was under the impression that these operations caused all MZScheme
threads to block.  Sounds like that's not the case.   Are there any
language/implemetation reasons why they also be done in parallel?

Thanks for clarifying this for me.  I would prefer to use MzScheme and
PLT (though god knows it would have been really nice if they were
compatible enough to support lazy implementation selection. )

On Wed, 12 Jan 2005 07:34:26 -0700, Matthew Flatt <mflatt at cs.utah.edu> wrote:
>   For list-related administrative tasks:
>   http://list.cs.brown.edu/mailman/listinfo/plt-scheme
> 
> At Wed, 12 Jan 2005 09:01:19 -0500, Larry White wrote:
> > I'm currently focusing on chicken scheme since their documentation
> > suggests that they don't necessarily block on I/O like PLT scheme
> > apparently does
> 
> Can you be a little more specific?
> 
> MzScheme supports non-blocking I/O, blocking I/O that doesn't block
> other MzScheme threads, and generalized select (a la Concurrent ML).
> 
> Matthew
> 
>