tbnl-devel January 2005

tbnl-devel@common-lisp.net

1 participants
2 discussions

[tbnl-devel] Handling HTTP errors
by Stefan Scholl 01 Mar '05

01 Mar '05

Hi! Function send-output in modlisp.lisp handles the response for different return codes. E. g. there's a "The requested URL ~A was not found on this server." for the 404 (+http-not-found+). How about letting the user change this behavior? One could explain the error to the user. Maybe in another language. Or think of all the funny 404 games. Remember the SGI babies? There could be different approaches: * Simple hash A hash with error code as key and handler as value. + Easy to implement + Can handle all errors (thrown by handlers _and_ when no dispatcher is found) - Not very flexible. Just checks for the code and not for any request data. * Error dispatcher Like the normal dispatcher, but checking for the right error output handler. + Can handle all errors (thrown by handlers _and_ when no dispatcher is found) + Flexible. Can check the code _and_ request data. - A bit big. The same effort like handling normal requests. * Handler outputs itself and signals that A handler wants to return a 404. It constructs the output string and signals the fact that there's no need for TBNL to build the HTML for the output. + Easy to implement(? clean?) + Flexible - Can't handle all errors. (No handler found? Then the code won't be executed.) Regards, Stefan

2 3

[tbnl-devel] New version 0.3.10
by Edi Weitz 24 Jan '05

24 Jan '05

Changelog: Version 0.3.10 2005-01-24 Make bivalent streams work with LispWorks 4.4 UTF-8 demo for LispWorks (thanks to Bob Hutchinson) Download: <http://weitz.de/files/tbnl.tar.gz> Cheers, Edi.

1 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

tbnl-devel January 2005