You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm new to the codebase, but I've been integrating Boa into a project of mine as the JS executor, and it's been stellar to work with! (I'm working off main, the new async job stuff is great)
I'm looking around to understand how everything is architected, but I'm curious if anyone knows off the top of their head how difficult it would be to build memory/environment serialization for Context/Vm state? What I'm looking to potentially be able to support is storing the memory state of an instantiation, and then allow it to be resumed by pulling the serialized memory from storage and restarting the Context in the exact state it was in before.
Looking for anyone that can tell me if this is just crazy out of scope, or potentially achievable with some work / a little guidance on what's needed.
From first pass look, it seems the Vm contains the stack and the global object, which should be serializable. Things that are host defined or registered from the host could be tricky, but even getting to a state where I can do it without support for host defined to start with would be great.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
-
I'm new to the codebase, but I've been integrating Boa into a project of mine as the JS executor, and it's been stellar to work with! (I'm working off main, the new async job stuff is great)
I'm looking around to understand how everything is architected, but I'm curious if anyone knows off the top of their head how difficult it would be to build memory/environment serialization for Context/Vm state? What I'm looking to potentially be able to support is storing the memory state of an instantiation, and then allow it to be resumed by pulling the serialized memory from storage and restarting the Context in the exact state it was in before.
Looking for anyone that can tell me if this is just crazy out of scope, or potentially achievable with some work / a little guidance on what's needed.
From first pass look, it seems the Vm contains the stack and the global object, which should be serializable. Things that are host defined or registered from the host could be tricky, but even getting to a state where I can do it without support for host defined to start with would be great.
Beta Was this translation helpful? Give feedback.
All reactions