On 10/9/07, Ted Husted <[EMAIL PROTECTED]> wrote: > So, in the same way that WebWork 2 became Struts 2, SmartURLs 2.1 will > become CodeBehind 2.1.
I'm fine with this on one condition: 100% backwards compatibility. Backwards compatibility is so crucial for convention-based designs, because there is no clear feedback to the user that changes have been made. If you change an API, you probably deprecate the old methods, which gives immediate feedback to the user that something has changed, and they can usually view the javadocs on the deprecated method to see the suggested fix. If you just remove a method, the compiler will immediately tell the user something has changed. With a convention-based system, things just stop working and the user has no immediate reason why or how to fix it. This is one reason I like the idea of moving the zero conf out to a plugin is it is easier to develop new convention-based systems, while allowing legacy apps to continue working using the older system. Don > > -Ted. > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
