By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
438,818 Members | 2,089 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 438,818 IT Pros & Developers. It's quick & easy.

Store large amount of data

P: n/a
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

Sep 23 '05 #1
Share this Question
Share on Google+
2 Replies


P: n/a
"Kiki" <ko****@globet.com> skrev i meddelandet
news:11**********************@g43g2000cwa.googlegr oups.com...
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?


Store the data server-side and use session variables, or store a key to the
server-side data in a cookie. Then populate the forms server-side.

--
Joakim Braun
Sep 24 '05 #2

P: n/a
Thanks for your post Joakim. I have considered what you said but i'd
like to see that as the last solution. I would prefer to do this
client-side using the server at a later stage, once the user wants to
place the order.

Sep 26 '05 #3

This discussion thread is closed

Replies have been disabled for this discussion.