Application service provider architecture

[J]

Hi group,
We're developing a hosted application that will be used by hundreds of
client companies, each with its own database. Our first release of this
product separated each customer into its own virtual directory with a copy of
the code (classic ASP/IIS 5). We want to design the next version so that
there is one virtual directory, one common copy of the code.

My question is: are we losing any application isolation by doing this?
Under IIS5 by separating each customer into a virtual dir, we created a
separate "application" that could be pooled or isolated. Under IIS 6, do we
have to do the same thing or is there a way to break a single "site" into
multiple application pools. It seems that the default is to have an
application pool per site.

Thanks for any thoughts

 

[Mark Schupp]

I think you could create separate virtual directories in IIS that point to
the same physical directory. Never tried it myself but I think I have seen a
message or two hear from people who have. You would need to have your
initialization code in global.asa check the virtual path being used so that
users are connected to the correct database.