[plt-scheme] embedded web browser vs Apache

It's another webserver; you would run it along with Apache in the same 
way you might run, say, thttpd, or any other webserver for that matter, 
along side Apache. There is configuration you will likely need to do on 
your host, as well as to the respective webservers.

The PLT Web Server documentation deals with this to some degree:

http://docs.plt-scheme.org/web-server/

Advantages? Well, you can write servlets in Scheme, and get a robust 
continuation engine to boot. Other than that, you're just as well off 
writing all your CGIs for Apache in C, or perhaps assembly if you really 
want them to run fast...

Kidding! Just kidding!

For advantages and related info, see

http://www.cs.brown.edu/~sk/Publications/Papers/Published/mfgkf-web-restructuring-cps-journal/
http://www.cs.brown.edu/~sk/Publications/Papers/Published/kfgf-model-web-inter-error/

And other papers hanging around the PLT group webpages.

M

Hendrik Boom wrote:
> But ever since I've been wondering -- does the Scheme embedded web
> [server] play nicely with Apache?  or with the HTML files set up to
> be served by Apache?  Can I run this one as well as Apache?  If so,
> how to they apportion the incoming http requests?
> 
> And -- are there advantages to using this one instead of Apache?