Re: PatternConflict exception

[Robert Burt <bburt@2ab.com>]

It is my impression that the patterns can either be edited for consistency
at registration time or the EvaluatorLocator can make a decision on which
of two conflicting patterns to use, or even to use both.  From the spec the
above seems to be an implementation decsision.  I personally would think
that an implentation could have better performance if it did the conflict
check at registration time, but that would be an implemenation decision.

So what is a conflict, well if I have the following two patterns:

A*
AB*

Then a resource name "ABigPile" could be matched by either pattern. An
implemenationa might choose to not make this a conflict and have AB* take
precedence or it could consider it to be a conflict.

Bottom line, it appears to be an implementation decision and it should have
a way of indicating the fact that it considers something to be a conflict.


Bob


At 10:36 AM 2/25/99 -0500, you wrote:
>Carol or Bob,
>
>Quick question on semantics of exception PatternConflict. The current
>description of the exception is as follows:
>
>"The PatternConflict exception is thrown by the PolicyEvaluatorLocatorAdmin
>when an register_resource_name_pattern() detects a pattern that conflicts
with
>an existing registered pattern."
>
>What kind of conflict do you have in mind, which could happen that will cause
>this exception to be raised?
>
>Thanks
>Konstantin
>
>----------------
>Broadcast message to hrac-rfp from Konstantin Beznosov
<beznosov@baptisthealth.net>.
>Go to http://cadse.cs.fiu.edu/omg/hrac-rfp to browse the mail list archive.
>

----------------
Broadcast message to hrac-rfp from Robert Burt <bburt@2ab.com>.
Go to http://cadse.cs.fiu.edu/omg/hrac-rfp to browse the mail list archive.