Alan Grover <[EMAIL PROTECTED]> writes:
> Could you talk a little bit more about the "select with other stuff"
> pattern? What kind of stuff?
Yes, here are two examples.
1. In gds-server.scm in guile-debugging, I have a process that needs
to accept both TCP connections from Guile client proce
Neil Jerram wrote:
> Alan Grover <[EMAIL PROTECTED]> writes:
>>The lazy-ness is really in taking advantage of patterns for list
>>processing. Perhaps I didn't give an example like:
>> (define list-of-http-transactions (mod_lisp some-port-listener))
>> (for-each handle-request list-of-http
Alan Grover <[EMAIL PROTECTED]> writes:
> Actually, your comments are interesting, since you assumed I meant a
> lazy-list at the per-header level.
Yes.
> Hmmm. Weird. Even intriguing: why read the rest of the request if
> you get to a header that you tells you to give up?
That's not a mainline
Neil Jerram wrote:
>> 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
Alan Grover <[EMAIL PROTECTED]> 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 se
On Mon, Sep 19, 2005 at 11:24:34PM -0400, Alan Grover wrote:
> Neil Jerram wrote:
> (much elision)
[...]
> > How would using threads reduce resource usage? Otherwise this all
> > makes sense.
AFAIU inter-thread communication is just easier. And forking a thread
might be easier on VM than forking
Neil Jerram wrote:
(much elision)
> It seems to me, though, that there is nothing especially lispy about
> the module (mod_lisp) which runs inside Apache. Presumably the Apache
> side of the protocol could be implemented in any language, or could be
> provided "native" by Apache itself?
It's in C
Alan Grover <[EMAIL PROTECTED]> writes:
> Mod_lisp is a module for the Apache web-server. Via a simple
> configuration, you can have Apache "forward" a request to a separate
> process. The mod_lisp protocol is very simple.
>
> The mod_lisp home is:
> http://www.fractalconcept.com/asp/tC2/sdataQvrZ
Neil Jerram wrote:
> Alan Grover <[EMAIL PROTECTED]> writes:
>>* Should I remove the thread-creation stuff and stick simply to mod_lisp
>>protocol?
>
>
> I don't understand what the mod_lisp protocol is, so can't really
> comment. I'm interested in the architecture though - can you describe
>
Alan Grover <[EMAIL PROTECTED]> writes:
> Inspired by Guillaume Germain on the comp.lang.scheme group, I wrote a
> mod_lisp implementation for Guile. Find it at:
> https://sourceforge.net/project/showfiles.php?group_id=141512&package_id=163742
>
> I only implemented the mod_lisp protocol, leaving
Inspired by Guillaume Germain on the comp.lang.scheme group, I wrote a
mod_lisp implementation for Guile. Find it at:
https://sourceforge.net/project/showfiles.php?group_id=141512&package_id=163742
I only implemented the mod_lisp protocol, leaving query-string/POST and
HTML utilities for an exter
11 matches
Mail list logo
