From awgrover at mail.msen.com Wed Sep 14 18:27:21 2005 From: awgrover at mail.msen.com (Alan Grover) Date: Wed, 14 Sep 2005 14:27:21 -0400 Subject: [mod-lisp-devel] set help In-Reply-To: References: Message-ID: <43286B89.7030007@mail.msen.com> set show From awgrover at mail.msen.com Mon Sep 19 20:49:34 2005 From: awgrover at mail.msen.com (Alan Grover) Date: Mon, 19 Sep 2005 16:49:34 -0400 Subject: [mod-lisp-devel] awg-mod_lisp: mod_lisp for R5RS Scheme Message-ID: <432F245E.8040905@mail.msen.com> Announcing the release of awg-mod_lisp-0.2 (recently awg-mod_lisp-for-guile). Implements the elements of the scheme side of the mod_lisp2 protocol. Institutes as little policy as possible. Factored the protocol into a R5RS file. Also a test-daemon and higher-level daemon interface (in Guile). Available at https://sourceforge.net/project/showfiles.php?group_id=141512&package_id=163742 Limitations General: This code implements the mod_lisp protocol and does not parse the query-string, nor parse the POST data, nor provide a header-list that complies with the CGI interface, nor provide URL/HTML encode/decode functions, nor other high-level web-application functions. It doesn't even implement a socket-listener loop. See other files in this package. Content-length: As of 2005.09.17, mod_lisp2 (mod_lisp for Apache2) requires Content-Length to be computed before writing the content. Beware of the length of (newline). Is it \r, \r\m, \m, etc.? Character-Sets (utf): No explicit support, pretend that the right-thing will happen. See notes. Socket errors: What will happen if Apache is killed during a request? Or, if the socket has some other error? Mod_Lisp version: Written for mod_lisp2, circa 2005.09.17. Does not attempt to check the version (FIXME?). Perhaps next week I'll add a better high-level interface for Guile. From awgrover at mail.msen.com Tue Sep 20 12:05:42 2005 From: awgrover at mail.msen.com (Alan Grover) Date: Tue, 20 Sep 2005 08:05:42 -0400 Subject: [mod-lisp-devel] awg-mod_lisp: mod_lisp for R5RS Scheme Version 0.3 Message-ID: <432FFB16.40504@mail.msen.com> Version 0.3 of awg-mod_lisp, an R5RS implementation of the Scheme side of mod_lisp. Includes a Guile test daemon. Available at https://sourceforge.net/project/showfiles.php?group_id=141512&package_id=163742 Fix ARGV handling in the Guile test daemon. Include my debug module for same. -- Alan Grover From awgrover at mail.msen.com Tue Sep 20 12:06:37 2005 From: awgrover at mail.msen.com (Alan Grover) Date: Tue, 20 Sep 2005 08:06:37 -0400 Subject: [mod-lisp-devel] Re: awg-mod_lisp: mod_lisp for R5RS Scheme In-Reply-To: <1127210048.15694.11.camel@hobbes.mh-freiburg.de> References: <432F245E.8040905@mail.msen.com> <1127210048.15694.11.camel@hobbes.mh-freiburg.de> Message-ID: <432FFB4D.1050302@mail.msen.com> R. Mattes wrote: > Alan, there seem to be a vew bugs in this code. Thank you for finding & reporting them. Fixed in latest release. > First, the guile-specific module contains '(use-modules (awg debug))' > and a commented-out trivial debugging version. Since you don't > distribute your debugging module with the code it might be better to > have the 'use-module' part commented out and the trivial debugging > function enabled. I opted to include my debug module. > Second: i don't understand the following: > > (let* ( > (fn-name (or (and (pair? argv) (car argv) "once"))) > .... > > Isn't there a second argument to 'or' missing? > In the context of your sample code this always evals to "once". The 'and was only supposed to have two arguments, making "once" the default. > Kind of frustrating since the daemon only handles one request > and your suggested test > > ( sleep 1 ; wget -q -t 1 --post-data "post-data&foryou" ... > > fails. By "fails", I assume you mean because of the awg-debug module. Try with "thread", and the test daemon should keep listening now. -- Alan Grover awgrover at mail.msen.com +1.734.476.0969