I did not quite follow the recent discussion about path resolution in case there are multiple apps, but how about this: if you request /content/foo1/foo2 which does not exist microsling walks up the path till it finds an existing resource (say /content/foo1). It would then look for status404.esp at the location where it looks for other scripts that are relevant for /content/foo1 (i.e. depending on the resource type or so). But I think there are 2 open questions with this approach: - what do we do if there is no 404 handler at this location? Walk up the content tree? - how do we specify the mime type of the response? Should the script be named status404.html.esp?
On 12/13/07, Bertrand Delacretaz <[EMAIL PROTECTED]> wrote: > > On Dec 12, 2007 5:52 PM, Michael Marth <[EMAIL PROTECTED]> wrote: > > Re issue 1): > > > > we could have a 404 handler script that kicks in when a non-existing > > resource is requested.... > > Good idea. Do you have a suggestion about how to select which 404 script > to use? > > Assume I have dropped some scripts under /apps/foo, and I request > /content/foo which does not exist. > > IIUC you'd want in this case to use the /apps/foo/status.404.esp > script to handle this error, but how do we decide that this script is > more appropriate than, say, /bar/somewhere/404.esp? > > We might say that we replace the first level of the pathname (/content > in this case) with /apps, and use that as a starting point to look for > scripts. That's a simple enough rule, but it's a bit constraining. > > -Bertrand > -- Michael Marth, http://dev.day.com
