moving things out of the server (was: floats and efficiency)

Seth writes:
>... and while we're at it, can we finally move .location and .contents
>(and other spatial assumptions) out of the server?  This could be done
>in-DB, with the server's parser declining to work is there doesn't exist
>properly-formed .location and .contents properties where `player' is.

Similarly, why not do without the 'name' property on every object?

I am not suggesting this. What I mean to say is, that just as you don't
have to use floats just because they're there, you don't have to use the
location/contents system just because it's there. But I think most MOOs out
there actually use it.

Of course, it would be ideal if the server were so modular that you could
choose to leave such things out. But given that the MOO server purports to
provide a virtual object architecture, I think it makes just plain sense to
have every object in a given place.

Of all the server assumptions, I'd say the current location/contents model
is one of the most natural ones. Compare it to ownership, readability,
fertility, etc. Ownership is far more artificial; schemes for multiple
ownership abound - no need to tell *you* that! :)

     ____________________________________________________________
     Gustavo Glusman              Founder/administrator of BioMOO
     Gustavo@bioinfo.weizmann.ac.il    (public PGP key available)
     http://bioinfo.weizmann.ac.il/Gustavo
        Visit BioMOO, the biologists' virtual meeting place, at
     ___________ http://bioinfo.weizmann.ac.il/BioMOO ___________

---

References:

• Re: floats and efficiency
• From: "Seth I. Rich" <seth@Op.Net>

---

• Prev by Subject: Re: MOOcode level race condition with read() and force_input()
• Next by Subject: Re: moving things out of the server (was: floats and efficiency)
• Prev by thread: Re: floats and efficiency
• Next by thread: Non-standard Character sets question.
• Index(es):
  • Subject
  • Thread

Home |
Subject Index |
Thread Index