[MUD-Dev] about MOO

[Greg Miller]

Andru Luvisi wrote:
> Put simply: Whenever an object tries to do something restricted (ie read
> or write a file) your validator function (part of the mudlib in the two
> implementations I'm familiar with, Nightmare/Foundation and TubMud)
> examines the current call stack (the same one you'd see if you did a
> backtrace).  The functions don't matter, only the objects.  If *all* of
> the objects have the needed access, then the operation succeeds.  If *any*
> of them fail, the operation fails.  The only time the procedure is
> different is if an object specifically chooses to have *only* its access
> used for making the decision.  In the implementations I've seen, there 

This basically amounts to a capability system... Do a web search for
"capability system" and "eros" for a fairly detailed discussion of why
this approach works pretty well in many situations. (Eros is an
operating system that uses capabilities for its security rather than
user accounts).
--
http://www.classic-games.com/
Conspiracy theorists mistakenly assume others think before acting.
*** Please limit .sigs to four lines and avoid HTML mail or posts. ***



_______________________________________________
MUD-Dev maillist  -  MUD-Dev at kanga.nu
http://www.kanga.nu/lists/listinfo/mud-dev