I would go for SQL based data, either as:
- custom tables referenced by a custom session ID, which you could pass
between pages as request argument
- SQL-based Session object
Anyway, you'll find a better discussion of this issues in the "Managing
State in Web Applicactions" chapter of the "Design and Implementation
Guidelines for Web Clients" reference guide.
http://msdn.microsoft.com/library/de...forwc-ch05.asp
That's "free but very valuable" material provided by Microsoft's
"Prescriptive Arquitecture Guidance" group (PAG), lots of stuff available in
their site
www.microsoft.com/practices
Regards
Jose
"RA" <ron_a1@hotmail.com> escribió en el mensaje
news:u3d$2AU$DHA.1796@TK2MSFTNGP12.phx.gbl...[color=blue]
> Hi
>
> I use ASP.net with c#. The web application is hosted by a web host[/color]
provider.[color=blue]
> The application gets user information for order processing. The[/color]
information[color=blue]
> should be moved from one aspx page to the other until the user choose to
> submit the order. The order process has about 4 aspx pages. What will be[/color]
the[color=blue]
> best way to keep the user data between the pages considering the[/color]
following:[color=blue]
> 1) User might not have cookies enabled
> 2) I have no control on the IIS (managed by the web host provider)
> 3) I can use the sql server provided by the web host
> 4) Since it is user data it might have sensitive data
>
>
>
> Thanks
>
>[/color]
