Subject: Re: mod_lisp over CGI
From: rpw3@rpw3.org (Rob Warnock)
Date: Fri, 09 Nov 2007 23:26:23 -0600
Newsgroups: comp.lang.lisp
Message-ID: <n-GdnSum5c1i3ajanZ2dnUVZ_jidnZ2d@speakeasy.net>
Maciej Katafiasz  <mathrick@gmail.com> wrote:
+---------------
| skrev Rob Warnock:
| > If you want to maintain protocol compatibility with with "mod_lisp", you
| > probably don't want to change any of the other "#define"s in the source
| > [but if not, observe the effect of changing SOCK_PROTOCOL to
| > PROTOCOL_GETENV instead of PROTOCOL_MODLISP].
| 
| A bit of investigation shows that it's not a drop-in replacement for 
| actual mod_lisp. After writing a socket_connect() version for AF_INET, it 
| seems that Hunchentoot hates the values cgi_sock feeds it with, as they 
| are named quite differently than what mod_lisp provides. I was afraid of 
| that, and it was actually the part I wanted to avoid dealing with...
+---------------

Uh... Did you read the "Known bugs/errata/limitations:" section?
Where it says this?

  - Current "mod_lisp" protocol explicitly downcases the names of all
    environment variables before sending them; this program does not.

(Hint, hint...)


-Rob

-----
Rob Warnock			<rpw3@rpw3.org>
627 26th Avenue			<URL:http://rpw3.org/>
San Mateo, CA 94403		(650)572-2607