K
Kiki
Hello all,
i wonder if anyone can help with the following: I have an aspx page
that uses javascript to load some data which the user will select by
check boxes. An object is created containing information re that
selection. What is the best way of storing this object so it can be
accessed even in a postback? (e.g. the user selects his products, goes
to the next step, changes his/her mind, goes back to the original page
and the page is no longer populated with the selected items). I have
considered storing the object that gets created in a Cookie, by
converting it to a string and back to an object when i need it, but the
limitation of 20 name/value combination is too small. Is HTTPHandlers
the only other option?
Thanks is advance for your help and suggestions
i wonder if anyone can help with the following: I have an aspx page
that uses javascript to load some data which the user will select by
check boxes. An object is created containing information re that
selection. What is the best way of storing this object so it can be
accessed even in a postback? (e.g. the user selects his products, goes
to the next step, changes his/her mind, goes back to the original page
and the page is no longer populated with the selected items). I have
considered storing the object that gets created in a Cookie, by
converting it to a string and back to an object when i need it, but the
limitation of 20 name/value combination is too small. Is HTTPHandlers
the only other option?
Thanks is advance for your help and suggestions