Re: freeze/thaw an FSM instanc

[Jacob Beard]

Hi Matt,

This feature has come up a few times, and it's on my to-do list. I actually wrote up some documentation about how this would be implemented, which you can read here: https://github.com/jbeard4/SCION/wiki/Serialization-Deserialization-of-%22snapshots%22

Changes made to SCION following these guidelines would be mostly forward-compatible with SCION-ng.

I would estimate that this is only about a day of work to implement, but given the constraints of my current schedule, I think that it might be a few weeks before I'll be able to get to this. Patches are of course welcome.

Let me know if you have any questions. Thanks,

Jake

On Feb 28, 2013 7:17 PM, "Matt O" <matt....@gmail.com> wrote:

Hi, Jacob,

This is possibly similar to [1] from 7/23/2012.

We'd like the ability to save an idle FSM to persistent storage and to restore it at some point in the future with the same configuration and data model.

Any thoughts on how to achieve this with SCION present and/or future?

Reasonable to expose a pair of companion APIs that a) export the data model and the current state configuration to a JSON blob and b) create a new engine instance given the model and output from (a)?

Other approach?

Regards,
Matt

[1] https://groups.google.com/forum/?fromgroups=#!topic/scion-dev/5ClvNx8mGb4

--
You received this message because you are subscribed to the Google Groups "scion-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email to scion-dev+...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.