Hi,
I made a new test (serving a png and a js) with current trunk and the gap
is
much smaller now: tomcat is 25% faster on average.
Attila
Attila can you elaborate on your tests? Are you comparing the difference
between using a resource reference (js) and image component (png) in
wicket vs
2011/3/25 mzem...@osc.state.ny.us
Hi,
I made a new test (serving a png and a js) with current trunk and the gap
is
much smaller now: tomcat is 25% faster on average.
Attila
Attila can you elaborate on your tests? Are you comparing the difference
between using a resource reference
2011/3/24 hok ivanvasi...@gmail.com
2. In the Servlet 3.0 specification it's possible to have static resources
under META-INF/resources and I noticed that wicket has
MetaInfStaticResourceReference, which is better for serving static
resources. In my case for some components I have css files
Hi,
On Thu, Mar 24, 2011 at 7:17 AM, Attila Király kiralyattila...@gmail.comwrote:
2011/3/24 hok ivanvasi...@gmail.com
2. In the Servlet 3.0 specification it's possible to have static
resources
under META-INF/resources and I noticed that wicket has
MetaInfStaticResourceReference, which
You can attach a front-end proxy like nginx or apache that caches resources
delivered by your wicket application so subsequent requests will be served from
the proxy cache with maximum speed.
Am 24.03.2011 um 09:01 schrieb Martin Grigorov:
Hi,
On Thu, Mar 24, 2011 at 7:17 AM, Attila
2011/3/24 Martin Grigorov mgrigo...@apache.org
Hi,
On Thu, Mar 24, 2011 at 7:17 AM, Attila Király kiralyattila...@gmail.com
wrote:
2011/3/24 hok ivanvasi...@gmail.com
2. In the Servlet 3.0 specification it's possible to have static
resources
under META-INF/resources and I
For development you can keep the resources in the usual, wicket
preferred location (next to the class files), and when you package
your jars you can instruct your build tool to move them to
META-INF/resources
Best of both worlds :)
Martijn
On Thu, Mar 24, 2011 at 7:17 AM, Attila Király
Yes, but you would have to change how you refer to them, right?
On Thu, Mar 24, 2011 at 6:33 AM, Martijn Dashorst
martijn.dasho...@gmail.com wrote:
For development you can keep the resources in the usual, wicket
preferred location (next to the class files), and when you package
your jars you
On Thu, Mar 24, 2011 at 12:02 PM, James Carman
ja...@carmanconsulting.com wrote:
Yes, but you would have to change how you refer to them, right?
Not sure how that would work out, haven't tried it. Isn't this also a
tomcat specific optimization as well?
Martijn
On Thu, Mar 24, 2011 at 12:13 PM, Martijn Dashorst
martijn.dasho...@gmail.com wrote:
On Thu, Mar 24, 2011 at 12:02 PM, James Carman
ja...@carmanconsulting.com wrote:
Yes, but you would have to change how you refer to them, right?
Not sure how that would work out, haven't tried it. Isn't
looks like a refactoring-nightmare ...
Am 24.03.2011 um 12:23 schrieb Martin Grigorov:
On Thu, Mar 24, 2011 at 12:13 PM, Martijn Dashorst
martijn.dasho...@gmail.com wrote:
On Thu, Mar 24, 2011 at 12:02 PM, James Carman
ja...@carmanconsulting.com wrote:
Yes, but you would have to change
On Thu, Mar 24, 2011 at 2:19 PM, Peter Ertl pe...@gmx.org wrote:
looks like a refactoring-nightmare ...
Can you be more specific ?
I even see it easier to manage.
With wro.xml you have all resources specified in one place but in different
groupd.
With default Wicket approach you have a ResRef
12 matches
Mail list logo
