On 10/23/07, Howard Lewis Ship <[EMAIL PROTECTED]> wrote: > Let me repeat ... I have seven years of experience (in Tapestry) on how NOT > to be backwards compatible. T5 is all about ensuring future backwards > compatibility without compromising the ability to enhance the framework > going forward.
I am not familiar with T3/T4 - only T5 - but if one builds a framework to eliminate future incompatibilities would not it be possible to make a backward compatibility as well? I guess this would be a good test case for the functionality you are developing. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
