MOO-cows Mailing List Archive
Re: [SERVER] optional verb call by server
Date: Mon, 25 Mar 1996 20:37:52 PST
From: firstname.lastname@example.org (Richard Godard)
Content-Type: text/plain; charset="us-ascii"
>> potentially undesireable "side effects". For example move() always checks
>> accept(), among other things. One MOO that I've seen implemented the builtin
>> priority_post() to move things unconditionally. Perhaps either more
>> $server_options or new, simpler builtins could be added)
>For what it's worth, I wrote a trivial change to the way movement is
>handled for IdMOO. Instead of calling WHERE:accept(WHAT) as tradition
>dictates, the builtin calls #0:accept(WHAT, WHERE), and #0:accept is
>programmed to call WHERE:accept(WHAT) normally. I'd propose that people
>interested in de-side-effecting builtins follow that course instead of
>making an all-or-nothing server option.
Well I made a patch that allow to disable (from the db, through properties
on $server_options) any of those calls:
E.g. if $server_options.disable_initialize_call exist and is true, then a
call to create() will NOT make the server call new_obj: initialize...
This allow me that kind of wrapper:
obj = create(@args);
/* I'm happy, the obj.owners property is initialized, multiple ownership is
As you can see, it's not all or nothing... it just allow you to move a verb
call from the server to the db...
With $server_options.disable_accept_call == 1, you could write a wrapper
Doesn't it offfer as much flexibility if not more ?
Suggestions and comments are welcome.
Subject Index |