I'am a bit confusing about the use of Isolated Storage on an IIS server.

I understand the goal of Isolated Storage : provides a safe place to store data with no worry about how and where is this place.

Since Isolated Storage has a by-user and by-assembly approach, I'am not to wild about using it on a IIS server where applications have almost their own identity. I haven't really seen the interest of impersonating a web application and almost never seen impersonated web applications myself but this is my point of view.

Using Isolated Storage on a server mean :

• Using Isolated stores in \Documents and Settings\<user>\

• Which mean \Documents and Settings\Default User\ when the application pool is owned by Local System or Network Services I guess

• Which also mean Write rights on this folder for Local System or Network Services

• Using of impersonation

Regarding a web application (logic), these ideas are confusing me... Document and Settings ? Default User ? Enable impersonation just for storage ? No control about storage on server ? Uh ?

And then I'am a front of a dilema : use System.IO.Packaging (with Isolated Storage inside) on web applications or find an alternative ?

Am I wrong in my approach ? Did I miss something ?

Any point of view is appreciated and an explanation about the Isolated Storage with IIS philosophy could be an anwser.

Thanks !