that model is not really an LDM is it, that might as wlel be return
new Model(object); couple that with an item reuse strategy and youve
got a recipe for stale data.
-igor
On Thu, Oct 15, 2009 at 12:02 AM, ulf schneider u...@datenlabor.net wrote:
hi igor, yes it does. here is the code:
/**
Â
Exactly my words! You can always make stuff slow and memory consuming:)
2009/10/14 Michael Mosmann mich...@mosmann.de
Anyway, for now this is just an unsubstantiated claim. Could I write a
Wicket application that was slow and hard to scale? ABSOLUTELY! Could I
write one that was fast
maybe he can tell us which committers, because so far we are lost...
-igor
On Thu, Oct 15, 2009 at 12:14 AM, Maarten Bosteels
mbosteels@gmail.com wrote:
clients that had trouble getting Wicket to scale, and they even hired
committers to try to fix
Is it a statement about Wicket or about
Would it be possible to generate resource paths with a version string
in them so that browsers will cache resources, but request new ones
when a version has been bumped?
e.g.
http://example.com/resources/org.apache.wicket/wicket-1.4.1/wicket-ajax.js
We have already a setting that will append last modified time to resource URL.
-Matej
On Thu, Oct 15, 2009 at 6:19 PM, Martijn Dashorst
martijn.dasho...@gmail.com wrote:
Would it be possible to generate resource paths with a version string
in them so that browsers will cache resources, but
I saw this link being referenced recently. Ignore the name speed up
caching etc. The entry also talks about resource versioning etc.
This leads to another question though: How to get a version for each
resource? Using your application’s version (if you have one) might be
appropriate but depends
igor.vaynberg wrote:
matej and i (mostly matej) have been working on an clean room
implementation that we think will be simpler, cleaner, and allow users
to mangle their urls as much as they want.
I apologize for not having any technical feedback but I just wanted to pipe
in and mention
