On Mon, Apr 4, 2011 at 10:08 PM, Howard Lewis Ship <[email protected]> wrote:
> But a no-args activation method will still be a failure, and result in > HTML content (from the page, or from the exception page) being > streamed to the client instead of the requested content. We really > want to get a 404 down to the client, and the best way to do that is > to have the PageDispatcher return false (rather than process the > request and return true). To me the "correct" behavior is that if no activation context is matched a 404 error should be sent to the client. That's the current and actual behavior every web server out there produce in the case of a request to a resource not available. So I'm prone with the Igor idea and definitely would extend it to a default: If no activation context is matched a 404 error is thrown to the client, if a developer need to deal with various heterogeneous situation he could use EventContext or put a lot of different handler methods... Please don't add knowledge where not necessary. Cheers -- Massimo http://meridio.blogspot.com --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
