<html><head><style type="text/css"><!-- DIV {margin:0px;} --></style></head><body><div style="font-family:garamond,new york,times,serif;font-size:10pt;color:#000000;"><div>Included is a patch that incorporates the ability to have a request
specific reason phrase that allows one to use code such along the lines
of<br><br> (setf (return-code*) (make-custom-status 500 "some database query error")))<br><br>This
would override the templates and the cooked messages but only for that
request and is intended to be an answer to the "StatusDescription"
member of the HTTPResponse class in the <a target="_blank" href="http://asp.net/"><span class="yshortcuts" id="lw_1328065353_0">ASP.NET</span></a>
library. Essentially, a custom-status-t class has been added that
links a code with a reason phrase. The "make-custom-status" function
above is just a constructor to this new class. The "reason-phrase"
function is now a generic method that dispatches off both the
custom-status-t class and the previous numeric status codes to be
backward
compatible.<br><br>I also ended up changing the error code dispatch to
be CLOS based using eql dispatch instead of a case statement for the
various http-status-code values. It seems to be a trend to use generic
functions instead of a case statement in this situation, probably
because of a hash table type dispatch is used behind the scenes rather
than going from start to finish as in a case statement.<br><br>Cheers,<br><br>Kari <br></div>
</div></body></html>