Yah, he's right about the caching... so maybe not work it... however the solution someone posted was a ... hmm... Just in Time Resource kind of idea. which would still optimize for whatever page you were on (instead of bundling it all up into one giant file).

- Brill Pappin





On 10-Apr-09, at 2:55 AM, Jeremy Thomerson wrote:

I think that this response by Igor to another thread was supposed to be on
this one.  Either way, it fits this one.

it is much simpler and more efficient to set proper caching headers.
concatenating resources often does not work because different
components on different pages contribute different resources, so there
are a lot of variations of these huge files you may end up with and
would have to stream to the user over and over. yes, it would only be
one request per page, but it would be a huge one over and over as
opposed to being able to cache a lot of small resources and never
request them again.

-igor


--
Jeremy Thomerson
http://www.wickettraining.com



On Thu, Apr 9, 2009 at 9:06 AM, Eduardo Nunes <[email protected]> wrote:

Hi,

Is there a way to tell wicket to package all referenced javascripts
together, the same for the css? If there isn't this solution yet, can
anyone tell me where should I look for to implement it?

Thanks,
Eduardo S. Nunes

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]



Attachment: smime.p7s
Description: S/MIME cryptographic signature

Reply via email to