From: "Francois Rouaix" <frouaix@home.net>
To: "Caml-List@Inria.Fr" <caml-list@inria.fr>
Subject: RE: [Caml-list] Web Development with OCaml
Date: Wed, 11 Jul 2001 08:35:10 -0700 [thread overview]
Message-ID: <NFBBJPJKELEJMBOIHIDHEEOGCAAA.frouaix@home.net> (raw)
In-Reply-To: <3B4BE8CE.B246A7E8@texoma.net>
To add a few cents to the discussion
> 5. An OCaml Web Server. I don't know what's available here yet.
> I haven't had the time to research yet.
> This could be a very interesting option, especially if it's fast.
> This could easily be an excellent option to put behind Tux.
> Tux serves number 1. above and passes all dynamic services to this
> server.
Back in 1996, I had something called V6 running in OCaml; it was an HTTP
proxy with
a bunch of interesting features, and could serve as a Web server. However,
this was
a long time ago, and iI implemented only HTTP 1.0, not 1.1. Also, we didn't
have threads in
native mode in those days. The speed was still reasonable. I remember that I
could
easily use 60% of our 10 Mb/s network (network still being used by other
stuff in
the lab).
> Is there any interest in a mod_ocaml or a fast-cgi module for OCaml?
> I haven't a clue on how to develop either but could possibly learn. :)
> After learning OCaml (at least some) first.
Actually, I did start an mod_ocaml project a couple of years ago. I had the
core
working, meaning that I produce a very simple page with the module.
However, I stopped before moving forward because of the intricacy of
correctly
designing the whole thing (configuration, separation of name spaces between
user-modules, compilation and loading on demand, etc...).
Also, I had doubts about the usefulness of a mod_ocaml. In practice (meaning
in the real .com world, where I was working at the time), one uses multiple
tier architectures. And you want something in the frontend that is simple
enough
that non-real programmers can still tweak; something that only does layout,
and
no logic.
If someone is interested, I might be able to retrieve the source. There is
a good OReilly book on Apache modules (although Apache 2.0 may make
this obsolete altogether).
--f
-------------------
Bug reports: http://caml.inria.fr/bin/caml-bugs FAQ: http://caml.inria.fr/FAQ/
To unsubscribe, mail caml-list-request@inria.fr Archives: http://caml.inria.fr
next prev parent reply other threads:[~2001-07-11 15:52 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-07-10 0:01 Jimmie Houchin
2001-07-10 7:10 ` Jean-Christophe Filliatre
2001-07-10 7:15 ` Tom Hirschowitz
2001-07-10 8:19 ` David Mentre
2001-07-10 9:38 ` Alain Frisch
2001-07-11 5:49 ` Jimmie Houchin
2001-07-11 6:03 ` Alexander V. Voinov
2001-07-11 14:47 ` Jimmie Houchin
2001-07-12 1:58 ` John Max Skaller
2001-07-11 6:19 ` Alain Frisch
2001-07-11 9:09 ` Samuel Heriard Dubreuil
2001-07-11 14:11 ` Jimmie Houchin
2001-07-11 15:35 ` Francois Rouaix [this message]
2001-07-11 20:44 ` Gerd Stolpmann
2001-07-12 2:32 ` Jimmie Houchin
2001-07-13 5:37 ` William Chesters
2001-07-13 10:29 ` Alain Frisch
2001-07-13 11:16 ` Vitaly Lugovsky
2001-07-13 14:04 ` Xavier Leroy
2001-07-13 17:08 ` [web-caml] " Vitaly Lugovsky
2001-07-15 18:03 ` Ari Heitner
2001-07-15 20:19 ` Gerd Stolpmann
2001-07-16 8:23 ` wakita
2001-07-17 16:18 ` John Max Skaller
2001-07-17 18:50 ` Ari Heitner
2001-07-18 22:24 ` John Max Skaller
2001-07-13 16:12 ` Lyn A Headley
2001-07-13 17:50 ` William Chesters
2001-07-13 16:51 ` Miles Egan
2001-07-13 18:12 ` Jimmie Houchin
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=NFBBJPJKELEJMBOIHIDHEEOGCAAA.frouaix@home.net \
--to=frouaix@home.net \
--cc=caml-list@inria.fr \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox