Re: An analysis of mustUnderstand and related issues

Noah,

Thanks for taking the time to put this together; this looks great! A
few small comments below:

>  It is an error if any header referred to from dependsOn is not
> labeled either "mustHappen" or "hasHappened".

So we would not be able to express "headerA OR headerB" ? (That's
fine; just wondering.)

> Prior to processing any header carrying a "dependsOn" attribute, a
> check is made to ensure that each of the referenced headers
> "hasHappened"

I think you need an additional bullet that says that a given actor
processes headers according to the dependency graph (Yes, I know, this
is the basis of your "dependsOn" proposal, but I think went missing
from the list of bullets.).

> It is possible to impose dependencies on multiple headers destined
> for the same actor.  It is also possible to impose explicit
> dependencies on headers, including the body, destined for the
> anonymous actor.

And I guess it is possible to impose dependencies on multiple headers
destined at different actors? (Unless I am mistaken, this is, I think,
the subjet of your later example.)

Jean-Jacques.

Received on Monday, 14 May 2001 09:20:49 UTC