ehcache seems to be Apache licensed, so there is no immediate reason to put it into wicketstuff.
Given that the extensions project is used to mature components and features, I think it is a logical place for it to be in. But given the limited usage: it is only used for the markup cache, correct? Woould the second level cache be a second feature that could benefit from ehcache? Martijn On 7/15/07, Juergen Donnerstag <[EMAIL PROTECTED]> wrote:
no big plus, just playing a bit and having the option if some realy realy needs it.It should not go into the core project for sure. I'm just looking for the right place to drop it. If extension is not the right place either, due to the dependency, where should go? If not useful at all, we don't need to put it anywhere. Juergen On 7/15/07, Johan Compagner <[EMAIL PROTECTED]> wrote: > hmm i dont see the big plus, why would you have eviction? (except when the > file really changes) > The only eviction strategy i see that would be usefull is based if the > avaialable memory is used up > and it should free something. > > johan > > > On 7/15/07, Juergen Donnerstag <[EMAIL PROTECTED]> wrote: > > > > You can have all the out-the-box stats, jmx, eviction (remove if > > markup was not requested for >7 days) etc. > > > > Juergen > > > > On 7/15/07, Igor Vaynberg <[EMAIL PROTECTED]> wrote: > > > On 7/14/07, Juergen Donnerstag <[EMAIL PROTECTED]> wrote: > > > > > > > > I've created a ehcache based MarkupCache extension. On my laptop it is > > > > currently in wicket-extension which due to ehcache requires a ehcache > > > > dependency in pom.xml. I wonder whether wicket-extension realy is the > > > > right place? > > > > > > > > > what are the advantages of this over the one we have? > > > > > > -igor > > > > > > > > > > > > Juergen > > > > > > > > > >
-- Wicket joins the Apache Software Foundation as Apache Wicket Apache Wicket 1.3.0-beta2 is released Get it now: http://www.apache.org/dyn/closer.cgi/wicket/1.3.0-beta2/
