>Thanks for your reply Christophe,

>As I mentioned before serialising the state of the machine isn't an option for me, this is due to performance. I don't really need the >implementation internals of the state machine to be exactly as they were, just the ability to set up the data in my state classes and then set >the starting state.

>Doesn't the de-serialisation do something like this?

>Mark

Hi Mark,

Actually there is not much more of "internals" to serialize than the current states and your state's data (and only if you explicitly do it) so I doubt the performance would be much worse with serializing.