From: Gerd Stolpmann <info@gerd-stolpmann.de>
To: Jeff Henrikson <jehenrik@yahoo.com>
Cc: caml-list@inria.fr
Subject: Re: [Caml-list] jserv vs fastcgi
Date: 23 Apr 2003 18:26:36 +0200 [thread overview]
Message-ID: <1051115197.27493.127.camel@ares> (raw)
In-Reply-To: <35BDFDB4-732C-11D7-A75A-00039375801A@yahoo.com>
Am Son, 2003-04-20 um 14.32 schrieb Jeff Henrikson:
> I periodically hear commotion on this list about Jserv. Ocamlnet has a
> Jserv interface now I see. Can somebody explain to me what the
> advantages of Jserv are over FastCGI? FastCGI I know is old ('96), but
> it seems to serve my main goal, which is to keep my process alive so
> that I can pool ODBC connections. The specification is something that
> I can sit down and read in 30 minutes and understand:
>
> http://www.fastcgi.com/devkit/doc/fcgi-spec.html#S1
>
> I haven't seen a specification for just Jserv. Apparently it's
> superseded by the Java Servelet spec, which in version 2.4 is a 309
> page PDF file, chock full of bells and whistles which I haven't taken
> the time to taxonomize, specified in notation which I don't understand.
> It writes everything based on Java method calls, which doesn't give me
> a sense of what the actual data being passed along the channel is at
> all.
>
> I guess I also don't have a good sense of why FastCGI has been
> neglected enough to, for example, not be updated for HTTP 1.1 keepalive
> and etc. Though it sounds like there have been hacks to do this from
> time to time. The fastcgi mailing list seems to be fairly active.
>
> Would anybody with an understanding of this be so kind as to explain
> the big picture in a couple of paragraphs, if that's at all a
> reasonable request? My inclination right now is to sit down and write
> a fastcgi interface and configure Apache with mod_fastcgi, but I don't
> want to do that and find out I'm using a senselessly obsolete interface.
Well, when I selected the JServ protocol (=AJP), the main reason was its
simplicity. You don't need 309 pages to describe it, the network
protocol is much simpler (it's basically CGI over a socket).
Furthermore, many people used it, and it is included in every Linux
distro.
I never compared AJP with fastcgi, I just picked something that worked.
The disadvantage of AJP is that there have been numerous and frequent
updates of the protocol since AJP-1.2 (what I implemented for O'Caml).
Up to now, even the newest JK connector supports the old version 1.2,
but this will likely change some day, and we need an implementation for
a newer version.
Gerd
--
------------------------------------------------------------
Gerd Stolpmann * Viktoriastr. 45 * 64293 Darmstadt * Germany
gerd@gerd-stolpmann.de http://www.gerd-stolpmann.de
------------------------------------------------------------
-------------------
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
prev parent reply other threads:[~2003-04-23 16:26 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-04-20 12:32 Jeff Henrikson
2003-04-23 15:41 ` Noel Welsh
2003-04-23 16:26 ` Gerd Stolpmann [this message]
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=1051115197.27493.127.camel@ares \
--to=info@gerd-stolpmann.de \
--cc=caml-list@inria.fr \
--cc=jehenrik@yahoo.com \
/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