From: Adam W. <li...@co...> - 2002-07-16 02:26:10
|
On Mon, 2002-07-15 at 06:19, Sam Steingold wrote: > if you create a test case reproducible without apache, I can try to > debug it. Thanks for the offer of help Sam. I spent a while looking at how I would go about attempting to create my own version of mod_lisp for Apache 2 and learned a lot about apache module development in the process. But in the process I also realised that clisp is great for plain CGI development! Initial testing of using clisp as a CGI scripting language is impressive. I can load a simple initialisation program, access the environment variables within a shell and return the result to wget via Apache 2.0.39 in 0.18s on a Pentium 166 with 64MB of RAM. The initialisation file, init.lisp just contains: (format t "Content-type: text/html~2%") (princ "Hello from init.lisp") And is compiled with "clisp -c init.lisp" and is placed in the document root directory. The CGI file contains: #!/usr/bin/clisp (load (concatenate 'string (getenv "DOCUMENT_ROOT") "init.fas")) (princ "<pre>") (princ (shell "set")) (princ "</pre>") And returns the list of environment variables to the client. (NB to access environment variables individually refer http://clisp.sourceforge.net/clash.html) I consider I will be able to go a long way in providing rich content before I need to load the initialisation file persistently in a continually running clisp environment. It annoys me that each script has to contain: #!/usr/bin/clisp (load (concatenate 'string (getenv "DOCUMENT_ROOT") "init.fas")) To allow each CGI access to the required macros, etc. It would be nice if I could hack mod_cgi so that this initialisation text was included by the module (if for example the filename suffix was "lisp"). Regards, Adam |