#48 Owner versus controls regarding link_ok

[Amy Lear]

It'd be nice if the link_ok logic with regards to
programs was a bit more flexible, and made use of the
concept of 'controls'.
For instance, instead of requiring that the owner of
the trigger and the owner of the program be the same
thing (such as for propqueues) unless the program is
link_ok, allow the possibility that if the owner of the
trigger controls the program, then it may run
regardless of link_ok.
The basic logic here being that if they control the
program, regardless of ownership, then they can just
set the program link_ok anyway.

[Michael Pratte]

Logged In: YES
user_id=340748

As I see it, the reason non-LINK_OK programs don't run via
propqueues is for testing convience more than anything. For
example, if you've written a program that _listens to a largely
populated room, and it begins to fail (thus, spewing error
messages every time somebody talks), you can simply unset
it's LINK_OK flag. It will still react to you, allowing you to test
and repair it, but it will ignore everything else, allowing others
to talk and move about without getting tons of errors shot at
them.

I've found myself in this situation a number of times, and had
used LINK_OK to my advantage in each of those. Thus, I'm
against this request. To me, the amount of time it would save
keeping people from having to set the program LINK_OK, it
would add to those needing to later debug it should there be
a problem.

-Hinoserm