From: Ian Price <ianprice90@googlemail.com>
To: Greg Troxel <gdt@ir.bbn.com>
Cc: Guile Users <guile-user@gnu.org>
Subject: Re: guile-fcgi?
Date: Sun, 06 Jan 2013 10:39:03 +0000 [thread overview]
Message-ID: <87bod2tx2w.fsf@Kagami.home> (raw)
In-Reply-To: <rmi8v8oud9a.fsf@fnord.ir.bbn.com> (Greg Troxel's message of "Sun, 23 Dec 2012 08:08:49 -0500")
Greg Troxel <gdt@ir.bbn.com> writes:
> Is this still of any value? Is there a replacement?
There is no replacement fastcgi library, but Guile 2 does come with a
web server library, which tends to be run behind a reverse proxy.
> I am inclined to remove this from pkgsrc. Any reason not to?
I haven't ran it, but I find it hard to believe that it wouldn't be
severely bitrotten at this point.
--
Ian Price -- shift-reset.com
"Programming is like pinball. The reward for doing it well is
the opportunity to do it again" - from "The Wizardy Compiled"
prev parent reply other threads:[~2013-01-06 10:39 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-23 13:08 guile-fcgi? Greg Troxel
2012-12-24 2:25 ` guile-fcgi? Nala Ginrut
2012-12-24 14:08 ` guile-fcgi? Greg Troxel
2012-12-25 7:26 ` guile-fcgi? Nala Ginrut
2012-12-25 7:26 ` guile-fcgi? Nala Ginrut
2013-01-06 10:39 ` Ian Price [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
List information: https://www.gnu.org/software/guile/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87bod2tx2w.fsf@Kagami.home \
--to=ianprice90@googlemail.com \
--cc=gdt@ir.bbn.com \
--cc=guile-user@gnu.org \
/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 read-only IMAP folder(s) and NNTP newsgroup(s).