to reduce the number of requests required to serve a page.
as CSS Sprites! (see:
Xpedite Client Side Results
Xpedite will require no configuration XML (other than the web.config), no custom build tasks, no file write access on the file server, and by default, no custom code inserted in to your ASPX or code behind pages. With Xpedite you must only add a couple of handlers
When a resource is first requested, Xpedite will check to see if the resource has been cached on the server. If the file has been cached, the resource will be returned immediately to the client. If the file has not been cached, or if the modified date of the
requested file has changed, Xpedite will load the latest copy from the file system and cache the minified resource. As such, all compression and minification is done at run time without the need for custom build tasks. The memory requirement for caching the
Visual Studio 2010
Microsoft .NET Framework 2.0
Microsoft .NET Framework 3.5
ASP.NET WebForms (WebControls)
To achieve the above results, the application's web.config file was modified to add the CompositeResourceHandler and stock LINK, SCRIPT and IMG tags were replaced with Xpedite's CompositeResource and Sprite WebControls. Xpedite's
Sprite control can be directly swapped out for any IMG tag without impacting page layout.