Serialize is called on your script just before you leave a sim. You write everything you want to store to a StreamWriter or equivalent.
Deserialize is called when your script arrives at its new sim.
Clearly this is less transparent than using LSL, but on the one hand many scripts dont cross sim boundaries, or dont care about resets, and on the other hand this allows script developers to harness the speed and power of .Net today.
If someone provides a URL to the blog, I can post this there instead.
On 11/2/06, Jonathan <[EMAIL PROTECTED]
> wrote:
On Babbage's blog, it was stated that in was not easy to encapsulate a
CIL program's state into a packet to transfer to another sim as objects
move from sim to sim. That would explain why only one SL sim runs Mono
at this time. The VM I have may demostrate a solution to that.
Otherwise, it may provide the potential to host a local sim. These are a
few ideas.
_______________________________________________ libsecondlife-dev mailing list libsecondlife-dev@gna.org https://mail.gna.org/listinfo/libsecondlife-dev http://www.libsecondlife.org/
