Two quickies:

• Date: Mon, 22 Jan 1996 08:02:09 PST
• From:
  bartmoss <bartmoss@mistral.co.uk>
• Content-Type: TEXT/PLAIN; charset=US-ASCII

When a property is !c, its ownership is kept to be that of the original 
owner when somebody creates a child.
I also noticed that when you used I use a object size measurer it does 
not list the !c properties whos values have not changed. As soon as you 
change the value, even if to the same value it lists it and adds it to 
the total size.
I must mention that the verb used to measure the size is a hack from the 
byte_utils as the MOO uses object quota and not byte quota so this could 
be a quirk of the verb. But if it is not then it would be very useful to 
know.. I couldn't find any mention of this in the prog manual, but I 
would like to be certain.

Secondly, forks..
How attribitable to lag are they?
What I am getting at, is for something similar to the room message 
announcer. Lag wise, is it better to create forks for that room when 
people enter it and then kill them as they leave or to have one fork 
running the whole time sending messages to rooms in a list, say using a 
for loop?
Basically, I guess I am asking if any of you can explain the pros and 
cons to forks, and/or point me to some lititure on them.

Thanx,
Chris. 

• Prev: Trouble with $news
• Next: Re: Two quickies:
• Index: MOO-cows
• Thread: MOO-cows