Of disk swapping, database structure & project management..

Jeff Kesselman jeffk at tenetwork.com
Fri Apr 11 21:08:20 New Zealand Standard Time 1997

At 09:03 PM 5/1/97 +0100, you wrote:
>Has anyone experimented with swapping unused parts of the mud database to 
>disk, reading it back in when needed? What sort of format is it stored in 
>(eg binary, ASCII, etc)?

Cold does this automaticly.  it has a fixed memory footprint.
It writes out into a binary database (ndbm).  It also has a "text dump"
command that writes it all out in an ASCII form to transfer between systems
or edit.


>Also, what were your considerations when designing the structure of the 
>db (both memory and disk images) - ie i have a hex tree (like binary 
>tree, but with 16 child nodes instead of 2), but im not sure how 
>efficient it is.. a number of calculations have to be made to progress 
>down each 'level' of the tree, I was wondering what other ppl had done?

Cold is absed on the database, its really the center of the system.
"object ids" are really database record numbers.

>Now my project report has been handed in (phew) I can now accept 
>contributions from others. At the present time, there are about three or 
>four interested parties. Has anyone had any particularly good/bad 
>experiences related to project management in the area of mud development?
>The more I travel up the learning curve, the steeper it seems to get.. 
>ah, but I'll get there in the end (wont i??)
>        T  H  E     F  R  O  N  T  I  E  R  S     P  R  O  J  E  C  T   
>    http://www.uni-corn.demon.co.uk   telnet://linux2.cms.shu.ac.uk:9999
>   A student who changes the course of history is probably taking an exam

More information about the MUD-Dev mailing list