jacob_at_hookom.net wrote:
> Does the JS ever change or is it static?
>
Static.
> What's the overhead of pushing another request through JSF vs. sending the response down in one lot?
In the case where the browser requests the JS resource, the overhead is
small - we don't go through the full lifecycle.
The PL impact on non-JS requests is minimal.
> We're tweaking our own applications in an attempt to actually reduce the amount of external requests for JS/CSS/etc. Looking at some .NET apps, recieving 32k in a single request may prove more performant than 4 or 5 requests over the internet for the same amount of data (24k, 2k, 5k, 1k, 1k), each with a lag time of 16ms>100ms even with the caching headers.
>
What does the performance look like after the resources are cached?
There shouldn't be those extra requests.
>
>
>> So I'm curious what you all think about enabling
>> com.sun.faces.externalizeJavaScript by default.
>>
>> If enabled:
>>
>> - The default commandLink renderer will render an external script
>> reference for the commandLink JS
>> instead of inlining in the page
>> - A PL will be inserted into the lifecycle to intercept the external
>> JS request and serve the bytes
>> (caching headers are set, so the browser shouldn't be requesting
>> said bytes repeatedly)
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe_at_javaserverfaces.dev.java.net
>> For additional commands, e-mail: dev-help_at_javaserverfaces.dev.java.net
>>
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe_at_javaserverfaces.dev.java.net
> For additional commands, e-mail: dev-help_at_javaserverfaces.dev.java.net
>
>