Hi Dmitriy:
I think the chosen terminology caused some confusion. When you asked
for a technique to "cache page-level state", we assumed you meant
information that only needed to be around for the duration of the page
request. On the server side, the logical container for this would be
the HttpContext Item collection.
What I think you are looking for is really session state caching,
because it sounds like you need the information to outlive the
lifetime of a single page request and be available the next time the
client hits a page to get the editable DataSet object. In this case,
Session and Cache are the two built in mechanisms to keep state on the
server. The difference being that with cache, you'd have to scope the
entry to a specific user by keeping a user identifier in the cache
key.
HTH,
--
Scott
http://www.OdeToCode.com
On Fri, 3 Sep 2004 16:59:42 -0400, "Dmitriy Zakharov"
<dm********@yahoo.com> wrote:
ViewState is a hidden field on a form that stores anything as BASE64
encoded. The state information is bounced between client and server.
Its a good idea to store small non-critical objects in a ViewState.
Any ideas on bigger objects or sensitive information ?
Will you store temporary balance of someone's bank account in a client-side
ViewState ?
