From: Richard Jones <rich@annexia.org>
To: Joe Polanik <jPolanik@cds.duke.edu>
Cc: caml-list@inria.fr
Subject: Re: [Caml-list] Apache 2 and mod_ocaml
Date: Wed, 15 Dec 2004 21:17:13 +0000 [thread overview]
Message-ID: <20041215211713.GA21472@annexia.org> (raw)
In-Reply-To: <41C09C44.10800@cds.duke.edu>
[-- Attachment #1: Type: text/plain, Size: 937 bytes --]
On Wed, Dec 15, 2004 at 03:19:16PM -0500, Joe Polanik wrote:
> Is there a version of mod_ocaml for Apache 2? If so, where might this be
> found?
mod_caml or mod_ocaml? The two are different things. My summary of
the situation is here:
http://caml.inria.fr/archives/200410/msg00026.html
You need to patch Apache 2 to run mod_caml. See these instructions:
http://merjis.com/developers/mod_caml/apache_2.0
http://issues.apache.org/bugzilla/show_bug.cgi?id=27550
The process of getting the required patch into Apache 2.x is glacial,
but at least the developers are now showing some small amount of
interest.
Rich.
--
Richard Jones. http://www.annexia.org/ http://www.j-london.com/
>>> http://www.team-notepad.com/ - collaboration tools for teams <<<
Merjis Ltd. http://www.merjis.com/ - improving website return on investment
http://subjectlink.com/ - Lesson plans and source material for teachers
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2004-12-15 21:17 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-12-15 20:19 Joe Polanik
2004-12-15 20:57 ` [Caml-list] " Christophe TROESTLER
2004-12-15 21:17 ` Richard Jones [this message]
2004-12-16 8:24 ` Peter Busser
2004-12-16 9:30 ` Gerd Stolpmann
2004-12-16 11:39 ` Alex Baretta
2004-12-16 11:52 ` Richard Jones
2004-12-16 12:37 ` Alex Baretta
2004-12-16 13:45 ` Peter Busser
2004-12-16 16:36 ` Richard Jones
2004-12-16 18:10 ` Alex Baretta
2004-12-17 8:25 ` Peter Busser
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=20041215211713.GA21472@annexia.org \
--to=rich@annexia.org \
--cc=caml-list@inria.fr \
--cc=jPolanik@cds.duke.edu \
/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;
as well as URLs for NNTP newsgroup(s).