[coyotos-dev] AppNotice

[Jonathan S. Shapiro]

On Sun, 2007-10-07 at 13:15 -0700, Charles Landau wrote:
> At 4:23 PM -0400 10/6/07, Jonathan S. Shapiro wrote:
> >On Sat, 2007-10-06 at 07:43 -0700, Charles Landau wrote:
> >  > I'm guessing it's just a word of bits. postNotice or's in bits.
> >>  getNotices waits for the word to be nonzero, then atomically gets the
> >>  word and clears it.
> >
> >Very close.
> >
> >getNotices() does not tell you what notices you have. getNotices() tells
> >you what notices your AppNotice capability can *send*. Those notices are
> >delivered as a conventional message using a specification-defined
> >protected payload and endpoint ID when the destination process next
> >enters a receiving state.
> 
> I think I see now.
> 
> Section 3.4 talks about the "target process". Does this mean the 
> process executing an open wait on the target endpoint?

Not quite. Open waits do not occur on any particular endpoint. What
makes them open is that the endpoint is unrestricted.

The target process, in this case, is the process named by the process
capability within the endpoint.

> The documentation at makeAppNotifier suggests I can create multiple 
> AppNotifier capabilities for the same endpoint with different 
> authorized notices. The set of authorized notices must be stored in 
> the capability.

Yes. It lives in what would otherwise be the protected payload field.

shap