MUD

MUD

[Jason Welbourne]

I am attempting to write a multi-user program.  Before I can start, I
need to know something about sharing data between any number of interface
programs.  I need them all to be able to share the same data collection,
with read and write permission, and I would like for this to be memory
based as opposed to having to searh a file for a specific room's
information every time it is accesed.  I am briefly familiar with the
shared passive pragma, but I am having some difficulties using it.  Am I
using the right thing, and if I am, what am I doing wrong.  BTW, I do
not know if this is of any importance, but I am using a Linux system,
and I need the data to remain in memory even while nobody is using the
interface program.  I also would like to have my procedures for
altering the Database be contained within the shared part to prevent
hacking of the database.  Any help would be appriciated.  Please send
replys to welbjas@sciences.aum.edu

        Jason Welbourne

Re: MUD

[Dale Stanbrough]

I had my first year students working of an interface that a mixture
of 1st and 2nd year students coded up. We didn't use shared passive at
all, we just put all of the data structures into a package body, and
provided interface routines for all of the code. 

There was the required locking on all the internal data structures, which
was accomplished by using a protected type based semaphore.

Used gnat 3.09 and the appropriate glade implementation.


Dale