So, I'm writing a MUD in Oz. This means that I have to assume that any
given object in the MUD could have been written by an arbitrarily
malicious person. But I still want to allow potentially destructive
things to occur.
Obviously, there needs to be some way to do access control, or something
like it. The easiest way is for a method to somehow be told the
identity of the calling object, but it needs to be in a non-forgeable
fashion.
So, is there any way for me to get this sort of information already
built into the language? Otherwise I'm either going to have to have a
central mediator of method calls or use public key crypto, I think.
Thanks for your help!
-Robin
-- http://www.digitalkingdom.org/~rlpowell/ BTW, I'm male, honest. le datni cu djica le nu zifre .iku'i .oi le so'e datni cu to'e te pilno je xlali -- RLP http://www.lojban.org/ - Please send submissions to users@mozart-oz.org and administriva mail to users-request@mozart-oz.org. The Mozart Oz web site is at http://www.mozart-oz.org/.