Eric,
I find it hard to disagree with you, being a fan of incremental, iterative development myself. I just regret all the energy and time that went into 2.0 API compatibility workarounds so far. If we go with 3.0 then I would like to see a few more 2.0 API breakages that had been turned down for the sake of maintaining 2.0 compatibility, especially in the exception handling framework. I would also suggest HttpMethod interface be completely gotten rid of and the abstract HttpMethodBase renamed to HttpMethod.
Oleg
Sure. I am in favour of that as well. CVS HEAD is still pre alpha and already IS breaking 2.0 compatibility. So I don't see why we should not go ahead and fix this damn baby...
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]