On 10/14/07, Felix Meschberger <[EMAIL PROTECTED]> wrote: > ...(2) I am not sure whether resolving the script with the request > extension is useful. Rather I would use the "selectors" of the request > URL (the dot-separated parts between the node path and the extension) as > further script selectors....
I thought a bit about this, and I suggest instead adding an additional requestFilter that computes the desired Content-Type for the response, and stores it in the SlingRequestContext. The default implementation could just use the extension or selectors to do this, but at the SlingServlet level you get a clean "Content-Type=text/html" which tells you what to generate, irrelevant of the way this was derived from the request. -Bertrand
