Possibly an oversight, or it just seemed like the best "default configuration" that would please the greatest number of users.
It's certainly something that can be debated, though we wouldn't be able to change the defaults to what you suggested until at least tap 4.2 as there aren't any deprecation warnings in place yet. On 7/26/06, Kevin Menard <[EMAIL PROTECTED]> wrote:
> -----Original Message----- > From: Howard Lewis Ship [mailto:[EMAIL PROTECTED] > Sent: Wednesday, July 26, 2006 12:41 PM > To: Tapestry development > Subject: Re: object pools and tapestry memory (solved I believe) > > For public sites, its really important to make use of > org.apache.tapestry.accepted-locales configuration property. > > http://tapestry.apache.org/tapestry4/UsersGuide/localization.html#localiza > tion.accepted-locales Hmm . . . I guess I missed that one. It would seem to me that the default should be to limit resource usage and if one wishes to support multiple locales, then use a configuration item. Is there any particular reason why this is not the case? -- Kevin --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
-- Jesse Kuhnert Tacos/Tapestry, team member/developer Open source based consulting work centered around dojo/tapestry/tacos/hivemind.
