I don't see this as a "last chance" ... we can define a new annotation with a better name and deprecate @ApplicationState, but still support it indefinitely.
I'm trying to stick to the absolutely essential work to get a release out; bad naming is ugly but workable. On Wed, Nov 5, 2008 at 9:59 AM, Daniel Jue <[EMAIL PROTECTED]> wrote: > Good Suggestion for ApplicationSessionObject. > > I usually don't like it when such a commonly used feature is changed this > "late" in the game. > My suggestion would be to have the old annotation deprecated for a while, > with the new Annotation in place. > > Furthermore, if a new annotation for Application State is created, don't > re-use the old name! > > On Wed, Nov 5, 2008 at 12:04 PM, César Lesc <[EMAIL PROTECTED]> wrote: > >> I think we must support both @ApplicationStateObject and the new >> annotation, but i suggest not to change de acronym ASO because is so >> widely used that would break a lot of useful searchs and is a common >> lingo in tapestry, so the new annotation may be >> @ApplicationSessionObject. >> >> César. >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: [EMAIL PROTECTED] >> For additional commands, e-mail: [EMAIL PROTECTED] >> >> > -- Howard M. Lewis Ship Creator Apache Tapestry and Apache HiveMind --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
