From: <kl...@ta...> - 2007-12-10 09:28:33
|
nigel wrote: > The Apache<->Modlisp implementation appears to basically talk to a running lisp image over a socket (serializing requests in some fashion, not sure). I conjectured a similiar approach: if the url ends in some extension, throw it over the wall via a socket to the lisp image, then return the answer. > > The CGI interface is an interesting thought too... Will take a look there > The choosen technical solution boils down to performance requirements, if the lisp (or external whatever) code is constantly invoked to perform very small tasks, a very tight integration, possibly in the same addr space as beam, is required, on the other hand if the amount of work done by each individual list/external call is considerable, the CGI approach is fine. To implement a CGI receiver ??? server ??? hmmm what do you call that in lisp would probably be completely straight forward. It could also make sense to use the fastcgi protocol. This requires yaws to also support fastcgi http://www.fastcgi.com/devkit/doc/fastcgi-whitepaper/fastcgi.htm which IMHO it really ought to do. As usual I then conclude with: Any takers, FastCGI anyone ? /klacke -- Claes Wikstrom -- Caps lock is nowhere and http://www.tail-f.com -- everything is under control cellphone: +46 70 2097763 |