# Web User State Management and Serialization

**URL:** <https://www.ruby-forum.com/t/web-user-state-management-and-serialization/70761>\
**Category:** Ruby\
**Created:** [October 2, 2006, 7:41pm UTC](https://www.ruby-forum.com/t/web-user-state-management-and-serialization/70761 "2006-10-02T19:41:40Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![jhoglund](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/j/5fc32e/32.png) [@jhoglund](https://www.ruby-forum.com/u/jhoglund)\
**Post date:** [October 2, 2006, 7:41pm UTC](https://www.ruby-forum.com/t/web-user-state-management-and-serialization/70761/1 "2006-10-02T19:41:40Z")

</div>

Hello,

I am currently playing with RoR and I wanted to get State Management  
in. If a user just shuts the browser down and starts it up again (+  
logs in), there should be anything back on the screen (anything that  
was there when the last response from the server arrived).

Is it a good Idea to use rubys Marshal.dump + Marshal.load [1] and  
then store the dumped thing somewhere? What about performance?

A user invokes an ajax action, a response is being generated - this  
happens very often - each time the “system” will mashal some instances.

Whats your thoughts about this?

[1] [Serialization - Wikipedia](http://en.wikipedia.org/wiki/Serialization#Ruby)