On Fri, 31 Aug 2007, Alfie John wrote:
> Hi again,
>> I think they should use multiple requests. Example:
>>
>> Page 1 loads CSS files A, B, and C
>> Page 2 loads A, D, E, and F
>> Page 3 loads A, B, and E
>>
>> If a user loads all three pages, and each CSS file is 10k, then in
>> the
>> concatenation scenario, they load 100k in 3 requests, whereas in the
>> individual files scenario, they load 50k in five requests.
>>
>> I suppose it depends on a number of other things too.
>
> This assumes that the user will visit a single page only once and no
> CSS caching is performed by the browser.
>
> If however the responses being concatenated differ for each request
> type, this will in effect invalidate the browser's CSS cache. Probably
> not what you want.
His solution makes these assumptions (presumably). You'll notice the
individual files scenario I mentioned doesn't, and is in fact saying
indirectly what you just said directly (thanks for articulating that for me :)
).
> Premature optimization is the root of all evil. Discuss.
Premature optimisation is an educational experience :).
---------------------------------------------------------------------
| Name: Tim Nelson | Because the Creator is, |
| E-mail: [EMAIL PROTECTED] | I am |
---------------------------------------------------------------------
----BEGIN GEEK CODE BLOCK----
Version 3.12
GCS d+++ s+: a- C++$ U+++$ P+++$ L+++ E- W+ N+ w--- V-
PE(+) Y+>++ PGP->+++ R(+) !tv b++ DI++++ D G+ e++>++++ h! y-
-----END GEEK CODE BLOCK-----
-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems? Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/
_______________________________________________
Mason-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/mason-users
