[Home] [Groups] - Message: [Prev in Group] [Next in Group]
23852: RE: [MUD-Dev] Question about copyovers.
[Full Header] [Plain Text]
From: "Zach Collins {Siege}" <zcollins@seidata.com>
Newsgroups: nu.kanga.list.mud-dev
Date: Fri, 17 May 2002 02:50:09 -0400 (EDT)
References: [1]
Organization: Kanga.Nu
On Thu, 16 May 2002 fred@clift.org wrote:
> The first is to have the existing server fork and exec making sure
> that the descriptors are set to live through an exec) and pass
> info about what descriptor is what (and auxilary info like where
> in the world they are etc) via environment variables,
> disk-storage, or command-line options or something.
I've been looking at a variation of this in the MUD I've been trying
to design. In it, players are a subclass of mobile object; the main
difference is that player objects have an attribute that accepts
either a socket or None, instead of a similar attribute linked to
the mob AI. So by forking a fresh copy into memory, the resident
player objects are also copied, socket file-descriptors and all.
Then again, since I'm writing it in Python, I can also write the
code to load, reload, and unload modules almost at will.
--
Siege
_______________________________________________
MUD-Dev mailing list
MUD-Dev@kanga.nu
https://www.kanga.nu/lists/listinfo/mud-dev