One cool thing in ASP.NET 2.0 is the concept of VirtualPathProviders. You need not have to serve your pages from a filesystem always. For example you can serve your pages from the database. The VirtualPathProvider supports CacheDependency based invalidation of your content. One quirk though is what if your web server is on a DMZ and cannot access the database? I wrote a provider for such a scenario. I wrote a WebServiceVirtualPathProvider. So far so elegant. But to provide invalidation you have to write some kludge code which I don't like. Has someone faced a scenario like this?
Powered by Qumana
0 comments:
Post a Comment