Hey,
I have deployed a lisp web site app. :) It runs pretty nicely. I am using CMUCL 19c and TBNL 0.9.10. Some of the dynamic pages service 45pages/sec at concurrency of 1000 (ab benchmark).
thanks Edi for TBNL and the CMUCL folks for CMUCL.
I need now to customize some things. I need to desperately get rid of the Internal Server Error page. If someone types in a url part of which triggers a prefix dispatcher then we get this simple "Internal Server Error" page with a info string at the bottom. I need to change both of these.
Any pointers on how to do these things? I redefined the tbnl::tbnl-info-string in my source. Now I get my output string AND the original tbnl string.
thanks,
Hi!
On Thu, 06 Jul 2006 15:44:20 +0530, quasi quasilists@gmail.com wrote:
I need to desperately get rid of the Internal Server Error page. If someone types in a url part of which triggers a prefix dispatcher then we get this simple "Internal Server Error" page with a info string at the bottom.
The dispatcher triggers an error? I can't believe that. I'm pretty sure the error happens in your handler somewhere. Have you tried to debug this?
http://weitz.de/tbnl/#*show-lisp-errors-p* http://weitz.de/tbnl/#*show-lisp-backtraces-p*
I need to change both of these.
Any pointers on how to do these things?
http://weitz.de/tbnl/#*http-error-handler*
I redefined the tbnl::tbnl-info-string in my source. Now I get my output string AND the original tbnl string.
Generally, you shouldn't cope with things that aren't exported unless you absolutely know what you're doing.
HTH, Edi.
On 6 Jul 2006, Edi Weitz spake thusly:
Hi!
On Thu, 06 Jul 2006 15:44:20 +0530, quasi quasilists@gmail.com wrote:
I need to desperately get rid of the Internal Server Error page. If someone types in a url part of which triggers a prefix dispatcher then we get this simple "Internal Server Error" page with a info string at the bottom.
The dispatcher triggers an error? I can't believe that. I'm pretty sure the error happens in your handler somewhere. Have you tried to debug this?
ooops! I was meaning the handler. I needed to see why it was screwing up. :) Thanks for the pointer. Invaluable. I need to read the docs more seriously.
http://weitz.de/tbnl/#*show-lisp-errors-p* http://weitz.de/tbnl/#*show-lisp-backtraces-p*
:) Solved all my problems absolutely.
Thanks a mill.
www.cleartrip.com is the website. index, flight search and hotel search pages come via TBNL+CMUCL. The search is done by a backend java app which is a bit shaky. They are working on it.
Generally, you shouldn't cope with things that aren't exported unless you absolutely know what you're doing.
yup.
-
Edi Weitz -
quasi