[This was a personal mail, but it really should be on the dev list (and there was nothing private in here from what I could see...)]
On Wed, Nov 17, 2004 at 09:55:42PM -0500, Fred wrote:
> the way they send e-mail, it's possible for those to backfire. If I
> understand your random thoughts, SC on S/O of 1.0 alone may not be a good
> idea.
It was more of a thought to determine which rules may be SC candidates.
> Would it be possible to add a tflag for a rule if it should SC? This way
> the devs have more control over which rules SC but may require more work on
> your part. I don't see a way to set priority using this but it's a way to
> tell this rule to SC if hit.
That was my plan actually. A SC tflag, and "nice" will specify which way the
message ought to be flagged. It's still not clear how the priorities will be
set, I'm thinking the easy thing is to leave everything with a priority of 0,
except SC rules which get a lower priority -- net rules would be slightly
higher, and if a rule has a priority set that overrides. That way you'd get a
decent priority determination automatically, with the ability to override as
necessary.
There'd have to be some logic for the subrules, so that if a meta rule is SC,
the subrules will run first. Perhaps subrules should always be run first
since they're usually pretty lightweight?
--
Randomly Generated Tagline:
"What if we take you with us? Put you on trial?
Zathras not of this time. You take, Zathras die. You leave, Zathras die.
Either way, it is bad for Zathras."
- B4 Commander & Zathras on Babylon 5 (Babylon Squared)
pgpFhEaweXce7.pgp
Description: PGP signature
