Does the YUI loader compiler exclude browser caching?

Question

So, if I use the YUI loader (on Yahoo servers) to work with JavaScript, and I tell him to use combinations, so several YUI widgets can be loaded by the browser in one request, does that make it much more difficult for the browser to cache JavaScript?

Say I have a website with two pages, and the first uses the YUI Calendar, Dialog, and Tree widgets, and the browser receives them all in one combined request from YUI servers.

The next page uses the calendar and the YUI dialog, but not the tree. Does this not mean that this is technically a different request to Yahoo servers now with a different query string? So these two widgets will be loaded again, even if they were used only on the first page?

In this case, is it better to have one request to the combo server, which will lead to one request (in most cases) of unbearable JavaScript? Or multiple requests for individual YUI components that can be cached?

(YSlow doesn't seem to say anything about this question.)

Answer 1

, -. http , . , - , async , , , . , , , HTTP- (, ). , - , IO , .

js , . , , A) , B) - .

, , YUI , , . , , .

, , , , . .

Answer 2

, , , , , .

YUI, script , javascript , :

YUI().use('*', function(Y) {
    // Any modules that were already loaded on the page statically will now be
    // attached and ready to use. YUI will not automatically load any modules
    // that weren't already on the page.
});

minification , , , , Uglify