On Sat, Nov 16, 2013 at 06:16:44PM +0100, james anderson wrote:

good evening;

Hi James,

neither a read through the pages on lists.common-lisp.net, nor a search through gmane's offering yielded anything substantive on facilities to be combined with hunchentoot for

• authentication : alternatively basic, token, and session based?
• content negotiation : resolving request headers against declared availability to yield effective content type, encoding, etc?
• structured response status generation : condition handler -> response status control structures?

when these operations cannot be delegated to a mediating server, is the common practice to code them form scratch?

You probably looked at the wrong floor ;-) Theses days, those tasks aren't part of the server itself but are handled by some web framework sitting on top of the server (some even run on multiple server implementations). So, maybe you need to look at Clack/Caveman/Weblocks et al. (note: I haven't used these for my projects, but I think I recall reading about sessions in Clacks documentation).

best regards, from berlin,

Cheers from Freiburg,

RalfD