http://code.msdn.microsoft.com/fastmvc/Project/ProjectRss.aspxLoad dynamic pages 5 to 20 times faster by compressing response on the fly. Serve static files &#40;js, html, css&#41; 10 to 100 times faster by compressing and caching their content. Improve repeated si...http://code.msdn.microsoft.com/fastmvc/Wiki/View.aspx?title=Home&version=6<div class="wikidoc"> <h1> Why FastMVC? </h1><ul> <ul> <li><b>Load dynamic pages 5 to 20 times faster by compressing response on the fly</b></li><li><b>Serve static files (js, html, css) 10 to 100 times faster by compressing and caching their content</b></li><li><b>Improve repeated site load time by maximizing caching on browser</b></li> </ul> </ul> <br /><h1> Problem </h1>There are several problems with ASP.NET MVC application when deployed on IIS 6.0:<br /> <br /><ul> <ul> <li>Extensionless URLs give 404 unless some URL Rewrite module is used or wildcard mapping is enabled </li><li>IIS 6.0 built-in compression does not work for dynamic requests. As a result, ASP.NET pages are served uncompressed resulting in poor site load speed. </li><li>Mapping wildcard extension to ASP.NET introduces the following problems: </li><ul> <li>Slow performance as all static files get handled by ASP.NET and ASP.NET reads the file from file system on every call</li><li>Expires headers doesn't work for static content as IIS does not serve them anymore. Learn about benefits of expires header from here. ASP.NET serves a fixed expires header that makes content expire in a day.</li><li>Cache-Control header does not produce max-age properly and thus caching does not work as expected. Learn about caching best practices from here. </li><li>After deploying on a domain as the root site, the homepage produces HTTP 404.</li> </ul> </ul> </ul> <br /><h1> Solution </h1>We need to write a custom static file handler that will cache small files like images, Javascripts, CSS, HTML and so on in ASP.NET cache and serve the files directly from cache instead of hitting the disk. Here are the steps:<br /> <br /><ul> <ul> <li>Install an HttpModule that installs a Compression Stream on Response.Filter so that anything written on Response gets compressed. This serves dynamic requests.</li><li>Replace ASP.NET's DefaultHttpHandler that listens on <b>.</b> for static files.</li><li>Write our own Http Handler that will deliver compressed response for static resources like Javascript, CSS, and HTML. </li> </ul> </ul> <br /><b>Download the latest code from &quot;Downloads&quot; tab</b><br /> <br /><h1> Read on </h1>Read details about this on my blog:<br /> <br /><a href="http://code.msdn.microsoft.com/fastmvc/Wiki/View.aspx?title=http%3a%2f%2fmsmvps.com%2fblogs%2fomar&amp;referringTitle=Home">http://msmvps.com/blogs/omar</a><br /> </div>oazabirMon, 30 Jun 2008 08:01:21 GMTUPDATED WIKI: Home 20080630Ahttp://code.msdn.microsoft.com/fastmvc/Wiki/View.aspx?title=Home&version=5<div class="wikidoc"> <h1> Why FastMVC? </h1><ul> <ul> <li><b>Load dynamic pages 5 to 20 times faster by compressing response on the fly</b></li><li><b>Serve static files (js, html, css) 10 to 100 times faster by compressing and caching their content</b></li><li><b>Improve repeated site load time by maximizing caching on browser</b></li> </ul> </ul> <br /><h1> Problem </h1>There are several problems with ASP.NET MVC application when deployed on IIS 6.0:<br /> <br /><ul> <ul> <li>Extensionless URLs give 404 unless some URL Rewrite module is used or wildcard mapping is enabled </li><li>IIS 6.0 built-in compression does not work for dynamic requests. As a result, ASP.NET pages are served uncompressed resulting in poor site load speed. </li><li>Mapping wildcard extension to ASP.NET introduces the following problems: </li><ul> <li>Slow performance as all static files get handled by ASP.NET and ASP.NET reads the file from file system on every call</li><li>Expires headers doesn't work for static content as IIS does not serve them anymore. Learn about benefits of expires header from here. ASP.NET serves a fixed expires header that makes content expire in a day.</li><li>Cache-Control header does not produce max-age properly and thus caching does not work as expected. Learn about caching best practices from here. </li><li>After deploying on a domain as the root site, the homepage produces HTTP 404.</li> </ul> </ul> </ul> <br /><h1> Solution </h1>We need to write a custom static file handler that will cache small files like images, Javascripts, CSS, HTML and so on in ASP.NET cache and serve the files directly from cache instead of hitting the disk. Here are the steps:<br /> <br /><ul> <ul> <li>Install an HttpModule that installs a Compression Stream on Response.Filter so that anything written on Response gets compressed. This serves dynamic requests.</li><li>Replace ASP.NET's DefaultHttpHandler that listens on <b>.</b> for static files.</li><li>Write our own Http Handler that will deliver compressed response for static resources like Javascript, CSS, and HTML. </li> </ul> </ul> <br /><h1> Read on </h1>Read details about this on my blog:<br /> <br /><a href="http://code.msdn.microsoft.com/fastmvc/Wiki/View.aspx?title=http%3a%2f%2fmsmvps.com%2fblogs%2fomar&amp;referringTitle=Home">http://msmvps.com/blogs/omar</a><br /> </div>oazabirMon, 30 Jun 2008 08:00:01 GMTUPDATED WIKI: Home 20080630Ahttp://code.msdn.microsoft.com/fastmvc/Wiki/View.aspx?title=Home&version=4<div class="wikidoc"> <h1> Why FastMVC? ! </h1><b>Load dynamic pages 5 to 20 times faster by compressing response on the fly</b><br /><b>Serve static files (js, html, css) 10 to 100 times faster by compressing and caching their content</b><br /><b>Improve repeated site load time by maximizing caching on browser</b><br /> <br /><h1> Problem ! </h1>There are several problems with ASP.NET MVC application when deployed on IIS 6.0:<br /> <br /><ul> <ul> <li>Extensionless URLs give 404 unless some URL Rewrite module is used or wildcard mapping is enabled </li><li>IIS 6.0 built-in compression does not work for dynamic requests. As a result, ASP.NET pages are served uncompressed resulting in poor site load speed. </li><li>Mapping wildcard extension to ASP.NET introduces the following problems: </li><ul> <li>Slow performance as all static files get handled by ASP.NET and ASP.NET reads the file from file system on every call</li><li>Expires headers doesn't work for static content as IIS does not serve them anymore. Learn about benefits of expires header from here. ASP.NET serves a fixed expires header that makes content expire in a day.</li><li>Cache-Control header does not produce max-age properly and thus caching does not work as expected. Learn about caching best practices from here. </li><li>After deploying on a domain as the root site, the homepage produces HTTP 404.</li> </ul> </ul> </ul> <br /><h1> Solution ! </h1>We need to write a custom static file handler that will cache small files like images, Javascripts, CSS, HTML and so on in ASP.NET cache and serve the files directly from cache instead of hitting the disk. Here are the steps:<br /> <br /><ul> <ul> <li>Install an HttpModule that installs a Compression Stream on Response.Filter so that anything written on Response gets compressed. This serves dynamic requests.</li><li>Replace ASP.NET's DefaultHttpHandler that listens on <b>.</b> for static files.</li><li>Write our own Http Handler that will deliver compressed response for static resources like Javascript, CSS, and HTML. </li> </ul> </ul> <br /><h1> Read on ! </h1>Read details about this on my blog:<br /> <br /><a href="http://code.msdn.microsoft.com/fastmvc/Wiki/View.aspx?title=http%3a%2f%2fmsmvps.com%2fblogs%2fomar&amp;referringTitle=Home">http://msmvps.com/blogs/omar</a><br /> </div>oazabirMon, 30 Jun 2008 07:59:18 GMTUPDATED WIKI: Home 20080630Ahttp://code.msdn.microsoft.com/fastmvc/Wiki/View.aspx?title=Home&version=3<div class="wikidoc"> !Why FastMVC?!<br /><b>Load dynamic pages 5 to 20 times faster by compressing response on the fly</b><br /><b>Serve static files (js, html, css) 10 to 100 times faster by compressing and caching their content</b><br /><b>Improve repeated site load time by maximizing caching on browser</b><br /> <br />!Problem!<br />There are several problems with ASP.NET MVC application when deployed on IIS 6.0:<br /> <br /><ul> <ul> <li>Extensionless URLs give 404 unless some URL Rewrite module is used or wildcard mapping is enabled </li><li>IIS 6.0 built-in compression does not work for dynamic requests. As a result, ASP.NET pages are served uncompressed resulting in poor site load speed. </li><li>Mapping wildcard extension to ASP.NET introduces the following problems: </li><ul> <li>Slow performance as all static files get handled by ASP.NET and ASP.NET reads the file from file system on every call</li><li>Expires headers doesn't work for static content as IIS does not serve them anymore. Learn about benefits of expires header from here. ASP.NET serves a fixed expires header that makes content expire in a day.</li><li>Cache-Control header does not produce max-age properly and thus caching does not work as expected. Learn about caching best practices from here. </li><li>After deploying on a domain as the root site, the homepage produces HTTP 404.</li> </ul> </ul> </ul> <br />!Solution!<br />We need to write a custom static file handler that will cache small files like images, Javascripts, CSS, HTML and so on in ASP.NET cache and serve the files directly from cache instead of hitting the disk. Here are the steps:<br /> <br /><ul> <ul> <li>Install an HttpModule that installs a Compression Stream on Response.Filter so that anything written on Response gets compressed. This serves dynamic requests.</li><li>Replace ASP.NET's DefaultHttpHandler that listens on <b>.</b> for static files.</li><li>Write our own Http Handler that will deliver compressed response for static resources like Javascript, CSS, and HTML. </li> </ul> </ul> <br />!Read on!<br />Read details about this on my blog:<br /> <br /><a href="http://code.msdn.microsoft.com/fastmvc/Wiki/View.aspx?title=http%3a%2f%2fmsmvps.com%2fblogs%2fomar&amp;referringTitle=Home">http://msmvps.com/blogs/omar</a><br /> </div>oazabirMon, 30 Jun 2008 07:58:41 GMTUPDATED WIKI: Home 20080630Ahttp://code.msdn.microsoft.com/fastmvc/Release/ProjectReleases.aspx?ReleaseId=1226Mon, 30 Jun 2008 07:55:40 GMTCREATED RELEASE: Version 1.0 (Jun 30, 2008) 20080630Ahttp://code.msdn.microsoft.com/fastmvc/Wiki/View.aspx?title=Home&version=2<div class="wikidoc"> <b>Problem</b><br />There are several problems with ASP.NET MVC application when deployed on IIS 6.0:<br /> <br /><ul> <ul> <li>Extensionless URLs give 404 unless some URL Rewrite module is used or wildcard mapping is enabled </li><li>IIS 6.0 built-in compression does not work for dynamic requests. As a result, ASP.NET pages are served uncompressed resulting in poor site load speed. </li><li>Mapping wildcard extension to ASP.NET introduces the following problems: </li><ul> <li>Slow performance as all static files get handled by ASP.NET and ASP.NET reads the file from file system on every call</li><li>Expires headers doesn't work for static content as IIS does not serve them anymore. Learn about benefits of expires header from here. ASP.NET serves a fixed expires header that makes content expire in a day.</li><li>Cache-Control header does not produce max-age properly and thus caching does not work as expected. Learn about caching best practices from here. </li><li>After deploying on a domain as the root site, the homepage produces HTTP 404.</li> </ul> </ul> </ul> <br /><b>Solution</b><br />We need to write a custom static file handler that will cache small files like images, Javascripts, CSS, HTML and so on in ASP.NET cache and serve the files directly from cache instead of hitting the disk. Here are the steps:<br /> <br /><ul> <ul> <li>Install an HttpModule that installs a Compression Stream on Response.Filter so that anything written on Response gets compressed. This serves dynamic requests.</li><li>Replace ASP.NET's DefaultHttpHandler that listens on <b>.</b> for static files.</li><li>Write our own Http Handler that will deliver compressed response for static resources like Javascript, CSS, and HTML. </li> </ul> </ul> <br /><b>Read on</b><br />Read details about this on my blog:<br /> <br /><a href="http://code.msdn.microsoft.com/fastmvc/Wiki/View.aspx?title=http%3a%2f%2fmsmvps.com%2fblogs%2fomar&amp;referringTitle=Home">http://msmvps.com/blogs/omar</a><br /> </div>oazabirMon, 30 Jun 2008 07:53:30 GMTUPDATED WIKI: Home 20080630A