From: Andy Wingo <wingo@pobox.com>
To: ludo@gnu.org (Ludovic Courtès)
Cc: guile-devel@gnu.org
Subject: Re: [PATCH] Exposing the HTTP server constructor and accessors
Date: Mon, 09 Mar 2015 22:06:48 +0100 [thread overview]
Message-ID: <87mw3lyj6f.fsf@pobox.com> (raw)
In-Reply-To: <87zj7thw0k.fsf@gnu.org> ("Ludovic \=\?utf-8\?Q\?Court\=C3\=A8s\=22'\?\= \=\?utf-8\?Q\?s\?\= message of "Wed, 04 Mar 2015 11:55:39 +0100")
On Wed 04 Mar 2015 11:55, ludo@gnu.org (Ludovic Courtès) writes:
> Was there any particular reason for not exposing ‘make-server-impl’ et
> al. in (web server)? If no, I’d like to expose them as well as the
> default implementation.
Sounds fine to me.
A
--
http://wingolog.org/
next prev parent reply other threads:[~2015-03-09 21:06 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-04 10:55 [PATCH] Exposing the HTTP server constructor and accessors Ludovic Courtès
2015-03-09 21:06 ` Andy Wingo [this message]
2015-03-10 8:03 ` Ludovic Courtès
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=87mw3lyj6f.fsf@pobox.com \
--to=wingo@pobox.com \
--cc=guile-devel@gnu.org \
--cc=ludo@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).