Re: Package all CSS and JS

[Brill Pappin]

Yes, I see your point... by including jquery with two different sets, you actually make it worse because it can't be cached anymore. You're only going to gain a minor advantage if you bundle the whole possible set (for the whole site) in one download, but I doubt it would be worth the trouble for what you'd gain from it.

- Brill Pappin





On 10-Apr-09, at 5:16 PM, Igor Vaynberg wrote:

my point is that the "just in time" thing will not work

suppose

on page A you use jquery and ext
on page B you use jquery and yui

using this just-in-time composition you will get two resources:
jquery+ext and jquery+yui - so you are trading 3 hits for two hits,
but transferring jquery twice.

even worse, consider on page B you have a dynamic header contributor
that sometimes adds mootools.

so now you have jquery+ext, jquery+yui, jquery+yui+mootools, in the
case of the latter you did not actually save a request to the server
because you still have the jquery+yui+mootools combo, but because you
are doing this caching the last request which was supposed to be just
for mootols now also has to carry jquery+yui.

wicket is very dynamic, which makes these kinds of page-oriented
caching strategies difficult. in order to work correctly everything
should be oriented around a component, not a page.

-igor


On Fri, Apr 10, 2009 at 1:44 PM, Brill Pappin <br...@pappin.ca> wrote:

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

are a lot of variations of these huge files you may end up with and

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

components on different pages contribute different resources, so there would have to stream to the user over and over. yes, it would only be

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

On Thu, Apr 9, 2009 at 9:06 AM, Eduardo Nunes <esnu...@gmail.com> wrote:

Hi,

Is there a way to tell wicket to package all referenced javascripts

anyone tell me where should I look for to implement it?

Thanks,
Eduardo S. Nunes

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org

together, the same for the css? If there isn't this solution yet, can

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org

smime.p7s
Description: S/MIME cryptographic signature