Perhaps, although I think it's more about preventing people from implementing interfaces on classes which really do something else. In any case, the common approach in many APIs is to strongly encourage people to implement ActionContext by extending ActionContextBase, and maybe that's reason enough.
um... "reason enough?" sorry, yet another ineloquent post.
All I meant to say was "maybe having ActionContextBase gives us enough play to change the API of ActionContext as necessary, as long as we add implementations to ActionContextBase"
Joe
--
Joe Germuska [EMAIL PROTECTED] http://blog.germuska.com "Narrow minds are weapons made for mass destruction" -The Ex
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
