I've created a LambdaMoo localhost to mess around with and learn how to code in this language, out of curiosity, is there a way to prevent a full reset upon shutdown of the localhost? I'm using an Ubuntu VM and Telnet connection to the default Wizard. Unfortunately I had a crash and lost a lot of the stuff I was messing around with. Is there a way to prevent this from happening again or can I expect to have this happen to me in the future.
You received this message because you are subscribed to the Google Groups "MOO Talk" group.
To unsubscribe from this group and stop receiving emails from it, send an email to MOO-talk+u...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/MOO-talk/db0b62be-9ea3-4ed5-a4e2-ef51c9c36dbe%40googlegroups.com.
@dump should work just fine if you are a $programmer..
To view this discussion on the web visit https://groups.google.com/d/msgid/MOO-talk/14ed8d67-8787-4615-b8a2-07e6a7eb2d74n%40googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/MOO-talk/76618c2a-e5e3-4b70-8536-548fe552dfd4n%40googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/MOO-talk/bb2a96e2-5a4c-4a23-a860-fefac2243b0dn%40googlegroups.com.
For what it's worth:
player data could very easily be stored as a restful API that each MOO would use to authenticate and validate players before getting a player ID and returnning that number. Toaststunt has CURl support, or you could exec curl to make the API call.
If all MOOs worked together, maybe even by exposing their own API, you could very easily make the MOO that handled the connection just proxy the new connection for where the player went. enter a portal from a->b->c? cool, a disconnects from b, then hands over the connection to c. Toaststunt's proxy protocol support makes this super easy and you could still translate across the data.
We also have JSON for translating and compacting data into
something that can be deserialized at the other end easily.
My point mostly in all of this is that we've progressed 30 years. Bandwidth isn't really the issue anymore, and lots of improvements to MOO have been made in the performance department, along with compiler optimizations. I was doing some simple profiling with my game and had about 50000 entities running around without much issue at all, once I tuned things a bit. There were also other things going on in the background. There are still certainly some issues, but offloading a lot of work to threaded builtins makes a huge difference.