Home > .NET Framework > ASP.NET 2.0 VirtualPathProviders

ASP.NET 2.0 VirtualPathProviders

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

Advertisements
Categories: .NET Framework
  1. No comments yet.
  1. No trackbacks yet.

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s

%d bloggers like this: