From: James Leifer <James.Leifer@inria.fr>
To: 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 09:18:26 +0200 [thread overview]
Message-ID: <r77659lcrb1.fsf@muscadet.inria.fr> (raw)
In-Reply-To: <20040620230758.GA13051@redhat.com> (Richard Jones's message of "Mon, 21 Jun 2004 00:07:58 +0100")
Richard Jones <rich@annexia.org> writes:
>> 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.
Hi Richard.
Thanks for your reply!
I'm confused whether "Bassically, yes" includes the part after my
"or" or not.
Let me see if I have this right: in order to support mod_caml's
current model of loading in new .cmo files, dynamic linking is
necessary, hence native is out of the question.
However, if one didn't want to *dynamically* load CGIs but statically
link the CGIs together with the mod_caml glue, is caml dynamic linking
still necessary for any *other* part of the mod_caml's design
(e.g. the interaction between mod_caml and Apache)?
Best,
-James
-------------------
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-21 7:18 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
2004-06-21 7:18 ` James Leifer [this message]
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=r77659lcrb1.fsf@muscadet.inria.fr \
--to=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).