Embedded Resource Pros/Cons

[Adam]

We are having an internal debate as to whether or now we should deploy the Prometheus controls with UseEmbeddedScripts and UseEmbeddedSkins enabled. It would be much faster to deploy with it turned on, because otherwise we would have to go through and change the setting on each of the controls and then move the skins and scripts out to the server. Opponents to the using embbeded resources are claiming the following as concerns:

1. Compressibility of the CSS/JS files,

2. When/how/if things are cached client side. (IF is the operative word?)

3. How a load balancer/load balancing situation would help/hurt

Can you provide any information as to how performance is affected by using embedded resources versus using static resources for the Prometheus controls?

Thanks,
Adam

[Pau]

I'm also thinking about this. I've read (here on telerk's site) that embedded resources aren't always the most performant way to go. 

http://blogs.telerik.com/blogs/todd_anglin/archive/2007/05/15/top_15_optimization_tips_and_tricks.aspx

Someone else may have a better understanding of the ASP.net architecture, but I would believe that embedded resources would be slower than a normal request -- since they're being fed thru the ASP.net ISAP filters.. and are not able to be fulfilled via the IIS HTTP (now in Kernel!) requests. (Thus, also not able to be cached, compressed, etc.)

[Basel Nimer]

link is not active anymore

can Telerik confirm any performance issues related to embedding resources?

does embedding prevent client side caching of JS, CSS and image files?