You'll need to cache both hits and misses and then it should be fine. On Thu, May 19, 2011 at 11:34 AM, Bas Gooren <b...@iswd.nl> wrote:
> You could always preload all strings, or preload sets of strings. This way > you'll have fewer database requests, and faster lookups since you'll have > everything you need in a local map. > > Bas > > Op 19-5-2011 8:23, schreef Mathias Nilsson: > > Thanks, >> >> My concern is also name component collition. The >> org.apache.wicket.resource.loader.ComponentStringResourceLoader iterates >> over the component stack to check for the values but that could leed to 10 >> times per text string and it would be a heavy load even if I implemented >> some sort of cache. ( Or used wickets in Localizer ). >> >> >> How did you go about name collition without sinking the database? >> >> -- >> View this message in context: >> http://apache-wicket.1842946.n4.nabble.com/IStringResourceLoader-database-implementation-tp3533408p3534888.html >> Sent from the Users forum mailing list archive at Nabble.com. >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org >> For additional commands, e-mail: users-h...@wicket.apache.org >> >> -- Martin Grigorov jWeekend Training, Consulting, Development http://jWeekend.com <http://jweekend.com/>
