On Wed, Apr 6, 2011 at 7:02 PM, Howard Lewis Ship <[email protected]> wrote:
> But what is the definition of "matched"? Without significant changes > to some public APIs to allow ValueEncoders to describe what they match > OR a brute force approach of catching exceptions as indicators of a > non-match we are left with only what the current APIs can do: match on > the NUMBER of page activation context values present in the extra > path. I simply thought about it as: check if there's a matching activation event handler method, if not it simply matter that it isn't a request for that page so a 404 should come up. And I'll go with what the ValueEncoders can do now without adding any extra notions to it, the current API is sufficient IMHO, I value a bad practice to overload a page with too much activation contexts which a dramatically different. Cheers. -- Massimo http://meridio.blogspot.com --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
