Subject: New release of the LambdaCore database

From: Pavel Curtis <[email-masked]>
Date: Mon, 2 Aug 1993 22:02:58 -0700

I have extracted a new release of the LambdaCore database from the running
LambdaMOO system and made it available for FTP from parcftp.xerox.com, in the
files

		pub/MOO/LambdaCore-02Aug93.db
		pub/MOO/LambdaCore-02Aug93.db.Z

One thing that I think is new in this release is all of the support for various
networky things, including auto-registration and Gopher access.

Coming soon: a bug-fix/patch release of the server to tide folks over until
1.8.0 is ready...

	Pavel

---

From: Larry Masinter <[email-masked]>
Date: Tue, 3 Aug 1993 16:50:18 -0700

Just for those who look: the core doesn't include any user interface
to gopher, just the raw $gopher support. I thought the user interface
slates etc, were just a bit too in flux to put them in the core at the
time.

---

From: "Jacqueline D. Hamilton" <[email-masked]>
Date: Tue, 3 Aug 1993 17:06:27 -0700

Just out of curiousity.  Is there a change log anywhere from
core to core, listing the exact changes?  Or... is this too much
work to even think about?  It'd be helpful for us that want to
keep our cores relatively current, tho.

Would also love to see a db converter program - i.e., a hacked up
MOO server that'd only do 2 things  (well 3, really):  read in a new
core db.  read in an older db, objects # (oldcore+1..max_object).
Dump out the "new" db.  On my moo and various others I've worked on,
we've been saving the object numbers say #73 (or whatever max core
is) to 100, or sometimes to 200, for future cores.  And dont put any
props on #0, but on a $ref object.  $ref.player, $ref.room, etc etc.
Ideally for portability and upgradability.... if only such a change
program existed to make the upgrade simpler.

-j.