From: Richard Jones <rich@annexia.org>
To: James Leifer <James.Leifer@inria.fr>
Cc: caml-list@inria.fr
Subject: Re: [Caml-list] mod_caml's bytecode restriction due to Apache or just CGI dyn'linking?
Date: Mon, 21 Jun 2004 00:07:58 +0100 [thread overview]
Message-ID: <20040620230758.GA13051@redhat.com> (raw)
In-Reply-To: <r77zn6xewpz.fsf@muscadet.inria.fr>
On Sun, Jun 20, 2004 at 11:38:32PM +0200, James Leifer wrote:
> So... Is the limitation to use bytecode due to the desire to support
> *dynamic* linking of CGIs or for other reasons?
Basically, yes. We would need a version of Dynlink supporting native
code.
> If only the former, then could one simply forgo this feature and
> *statically* link all the natively compiled CGIs together with the
> mod_caml glue to make a library that gets delivered to Apache? If
> the price is that I have to restart Apache when changing my CGIs I
> would be willing to pay it.
'Tis possible. However I don't have any applications where having
natively compiled CGIs would make any noticable difference, so this
isn't the sort of thing which Merjis would develop. However if you
have patches ...
Rich.
--
Richard Jones. http://www.annexia.org/ http://www.j-london.com/
Merjis Ltd. http://www.merjis.com/ - improving website return on investment
MAKE+ is a sane replacement for GNU autoconf/automake. One script compiles,
RPMs, pkgs etc. Linux, BSD, Solaris. http://www.annexia.org/freeware/makeplus/
-------------------
To unsubscribe, mail caml-list-request@inria.fr Archives: http://caml.inria.fr
Bug reports: http://caml.inria.fr/bin/caml-bugs FAQ: http://caml.inria.fr/FAQ/
Beginner's list: http://groups.yahoo.com/group/ocaml_beginners
next prev parent reply other threads:[~2004-06-20 23:08 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-20 21:38 James Leifer
2004-06-20 23:07 ` Richard Jones [this message]
2004-06-21 7:18 ` James Leifer
2004-06-21 4:46 ` Basile Starynkevitch [local]
2004-06-21 7:33 ` James Leifer
2004-06-21 7:51 ` Basile Starynkevitch [local]
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=20040620230758.GA13051@redhat.com \
--to=rich@annexia.org \
--cc=James.Leifer@inria.fr \
--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;
as well as URLs for NNTP newsgroup(s).