From: Andy Wingo <wingo@pobox.com>
To: Thien-Thi Nguyen <ttn@gnuvola.org>
Cc: guile-user@gnu.org, Neil Jerram <neil@ossau.uklinux.net>
Subject: Re: Serving files with guile web server
Date: Thu, 31 Mar 2011 16:23:30 +0200 [thread overview]
Message-ID: <m3d3l7xtb1.fsf@unquote.localdomain> (raw)
In-Reply-To: <8762rb5yho.fsf@ambire.localdomain> (Thien-Thi Nguyen's message of "Tue, 22 Mar 2011 09:51:47 +0100")
On Tue 22 Mar 2011 09:51, Thien-Thi Nguyen <ttn@gnuvola.org> writes:
> If efficiency is a concern, another approach is to wrap
> sendfile(2) or something like it.
IMHO we should bind sendfile(2) in Guile itself.
Andy
--
http://wingolog.org/
next prev parent reply other threads:[~2011-03-31 14:23 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-16 23:33 Serving files with guile web server romel
2011-03-17 14:55 ` romel
2011-03-19 2:20 ` Neil Jerram
2011-03-19 16:47 ` romel
2011-03-19 18:17 ` Neil Jerram
2011-03-19 22:23 ` romel
2011-03-31 14:44 ` Andy Wingo
2011-03-22 8:51 ` Thien-Thi Nguyen
2011-03-31 14:23 ` Andy Wingo [this message]
2011-03-31 15:09 ` Andy Wingo
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=m3d3l7xtb1.fsf@unquote.localdomain \
--to=wingo@pobox.com \
--cc=guile-user@gnu.org \
--cc=neil@ossau.uklinux.net \
--cc=ttn@gnuvola.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).