From: Neil Jerram <neil@ossau.uklinux.net>
Cc: guile-user@gnu.org
Subject: Re: mod_lisp for guile
Date: Sun, 04 Dec 2005 10:07:36 +0000 [thread overview]
Message-ID: <87oe3xgopj.fsf@ossau.uklinux.net> (raw)
In-Reply-To: <432F80F2.4080605@mail.msen.com> (Alan Grover's message of "Mon, 19 Sep 2005 23:24:34 -0400")
Alan Grover <awgrover@mail.msen.com> writes:
> I look forward to your work on the issue. :) I kind of like the
> lazy-list solution, but I've been infected by a pure-and-lazy
> programming language (Clean). I think some people call them generators.
>
> I'm liking the lazy-list idea more and more. It seems to work well with
> the tcp-socket listener pattern.
Hi Alan,
I'm just picking up my interest in this again, and I can't see why you
think the lazy list approach will be practical. For two reasons:
1. If you are going to reuse the Apache socket (i.e. Keep-Socket: 1),
you need to read, sooner or later, all the available data for the
current request, so you might as well read it all upfront and then
present it to the caller as an alist.
2. Even if you're not reusing the Apache socket, you don't know where
a given header will be in the stream. So the chances are your
caller will have to read most of the available data anyway in order
to find the headers that it is interested again. So again, might
as well read the whole lot upfront and provide a more convenient
interface.
Have I missed something or misunderstood you?
Regards,
Neil
_______________________________________________
Guile-user mailing list
Guile-user@gnu.org
http://lists.gnu.org/mailman/listinfo/guile-user
next prev parent reply other threads:[~2005-12-04 10:07 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-09-15 17:25 mod_lisp for guile Alan Grover
2005-09-16 18:46 ` Neil Jerram
2005-09-19 14:46 ` Alan Grover
2005-09-19 21:32 ` Neil Jerram
2005-09-20 3:24 ` Alan Grover
2005-09-20 4:44 ` Threads (was: mod_lisp for guile) Tomas Zerolo
2005-09-20 12:12 ` Threads Alan Grover
2005-12-04 10:07 ` Neil Jerram [this message]
2005-12-05 17:21 ` mod_lisp for guile Alan Grover
2005-12-15 23:21 ` Neil Jerram
2005-12-16 13:21 ` Alan Grover
2005-12-29 10:18 ` Neil Jerram
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=87oe3xgopj.fsf@ossau.uklinux.net \
--to=neil@ossau.uklinux.net \
--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).