From: Mike Hamburg <hamburg@fas.harvard.edu>
To: Alex Baretta <alex@barettadeit.com>
Cc: Caml-list <caml-list@inria.fr>
Subject: Re: [Caml-list] CamlGI question
Date: Mon, 18 Apr 2005 23:23:14 -0400 [thread overview]
Message-ID: <426479A2.1020404@fas.harvard.edu> (raw)
In-Reply-To: <4263E01D.5090705@barettadeit.com>
I have ported my application to NetCGI, and it works as a CGI script,
just as it did under OCamlGI. However, if compiled as a FastCGI script,
it denies connections from the server and then dies (broken pipe). I'd
rather run the cgi as a standalone application, preferably FastCGI as
that's in my server, but if the FastCGI code in NetCGI doesn't work, I'd
be fine compiling it as AJP.
How should I either
(1) fix a broken pipe error in NetCGI or
(2) fix the broken pipe?
Thanks again,
Mike Hamburg
Alex Baretta wrote:
> Michael Alexander Hamburg wrote:
>
>> Given then that my application should be multithreaded, and will be
>> running on a webserver using Rails (which traditionally uses FastCGI),
>> which of these libraries do you suggest that I use? Http, Netcgi_afp or
>> Netcgi_fcgi? Or are they interoperable enough that it doesn't matter?
>
>
> So long as you use Netcgi, it does not matter. The API does not expose
> the difference between the various connectors.
>
> Alex
>
next prev parent reply other threads:[~2005-04-19 3:24 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-04-18 6:15 Mike Hamburg
2005-04-18 7:29 ` [Caml-list] " Robert Roessler
2005-04-18 13:49 ` Alex Baretta
2005-04-18 14:31 ` Gerd Stolpmann
2005-04-18 16:04 ` Michael Alexander Hamburg
2005-04-18 16:28 ` Alex Baretta
2005-04-19 3:23 ` Mike Hamburg [this message]
2005-04-19 3:26 ` [Caml-list] CamlGI question [doh] Mike Hamburg
2005-04-19 9:18 ` Gerd Stolpmann
2005-04-19 15:28 ` Mike Hamburg
[not found] ` <1113933973.6248.76.camel@localhost.localdomain>
2005-04-19 18:44 ` Eric Stokes
2005-04-19 19:18 ` Christophe TROESTLER
2005-04-19 21:11 ` Eric Stokes
2005-04-19 9:31 ` Alex Baretta
2005-04-19 11:33 ` [Caml-list] CamlGI question Christophe TROESTLER
2005-04-19 12:51 ` Christopher Alexander Stein
2005-04-19 19:03 ` Common CGI interface (was: [Caml-list] CamlGI question) Christophe TROESTLER
2005-04-19 19:54 ` Gerd Stolpmann
2005-04-20 6:55 ` Jean-Christophe Filliatre
2005-04-20 7:22 ` Common XML interface (was: Common CGI interface) Alain Frisch
2005-04-20 11:15 ` [Caml-list] " Gerd Stolpmann
2005-04-20 11:38 ` Nicolas Cannasse
2005-04-20 13:23 ` Stefano Zacchiroli
2005-04-21 6:59 ` [Caml-list] Common XML interface Alain Frisch
2005-04-21 11:34 ` Gerd Stolpmann
2005-04-20 20:00 ` Common CGI interface Christophe TROESTLER
2005-04-20 21:06 ` [Caml-list] " Gerd Stolpmann
2005-04-21 7:36 ` [Ocamlnet-devel] " Florian Hars
2005-04-21 10:41 ` Gerd Stolpmann
2005-04-25 10:38 ` Christophe TROESTLER
2005-04-26 11:08 ` Gerd Stolpmann
2005-05-06 20:14 ` Christophe TROESTLER
2005-05-10 0:07 ` [Caml-list] " Christophe TROESTLER
2005-05-10 0:10 ` Christophe TROESTLER
2005-04-26 16:24 ` [Caml-list] " Eric Stokes
2005-05-06 20:14 ` Christophe TROESTLER
2005-04-19 20:13 ` [Caml-list] CamlGI question Michael Alexander Hamburg
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=426479A2.1020404@fas.harvard.edu \
--to=hamburg@fas.harvard.edu \
--cc=alex@barettadeit.com \
--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