[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
RE: ordering constraints / procedures
> -----Original Message-----
> From: Robert Story [mailto:firstname.lastname@example.org]
> 1) SMIng must provide a mechanism to formally express
> ordering constraints.
> 2) SMIng should support a mechanism to formally define
> procedures that are
> used by managers when interacting with an agent.
> Can someone explain if there is a difference between these
> two? If they are
> the same, I vote that the "ordering constraints" name is clearer than
[Dave] Yep, I believe this is what was decided in the WG meeting as well.
"Procedures" will go away unless someone comes up with a distinction.
> Also, I was wondering how any constraints would be enforced.
> If they entail
> multiple sets, then this could be the createAndWait problem
> all over again.
[Dave] Quite possibly. If no one can establish a clear value or use for this
requirement than it will not be included in the final Requirements document.
My understanding was that ordering would help to avoid CreateAndWait because
you are specifying which combination of sets go together and in what order
as a transactional semantic, to be enforced by the management station.