English version
Accueil     À propos     Téléchargement     Ressources     Contactez-nous    

Ce site est rarement mis à jour. Pour les informations les plus récentes, rendez-vous sur le nouveau site OCaml à l'adresse ocaml.org.

Browse thread
Sample web server with nethttpd
[ Home ] [ Index: by date | by threads ]
[ Search: ]

[ Message by date: previous | next ] [ Message in thread: previous | next ] [ Thread: previous | next ]
Date: 2007-03-30 (14:38)
From: Joel Reymont <joelr1@g...>
Subject: Sample web server with nethttpd
I'm trying to bring up a web app as soon as possible and failing to  
link Ruby with OCaml code my choice is to decouple and put an app  
server behind Rails. Apache is heavy-weight so mod_caml is out of the  
question. The choice is nethttpd and Ocsigen.

My OCaml app server needs to take a POST request, grab the posted  
source code, translate it and spit it out. I can't figure out how to  
bring up a web server with nethttpd, though.

It would be extremely helpful to have an expanded nethttpd tutorial 
[1] that included a sample web server. I read through but writing  
efficient code to accept connections in OCaml seems daunting and the  
choice between engine and reactor unclear.

There's a sample web server in the Netplex intro, though[2], is that  
sufficient? Maybe the nethttpd intro should just point to the Netplex  

Quoting the manual:
 >>> Second, select an encapsulation.

How is this done, precisely?

 >>> As mentioned, the reactor is much simpler to use, but you must  
take a multi-threaded approach to serve multiple connections  

What's the standard (optimal) pattern here? Are there any code samples?

 >> The engine is more efficient, but may use more memory (unless it  
is only used for static pages).

How much more memory? Is there a rule of thumb?

How should I decide whether to pick an engine or a reactor?

 >>> Third, write the code to create the socket and to accept  

Should I use the netplex intro sample code?

 >>> For the reactor, you should do this in a multi-threaded way (but  
multi-processing is also possible). For the engine, you should do  
this in an event-based way.

It appears that web servers like Lighttpd use the event-based way,  
should I pick that?

	Thanks, Joel

[1] http://ocamlnet.sourceforge.net/manual-2.2/Nethttpd_intro.html
[2] http://ocamlnet.sourceforge.net/manual-2.2/Netplex_intro.html