[coyotos-dev] AppNotice

[Jonathan S. Shapiro]

On Sat, 2007-10-06 at 07:43 -0700, Charles Landau wrote:
> >Sorry. AppNotice is the one. It eliminates the need for a helper thread.
> 
> That sounds useful, but the documentation is unclear. postNotice is 
> mentioned but not documented. Also a couple of typos:
> App capability -> AppNotice capability
> ones -> once

Thanks. Actually, postNotice was documented in the IDL file, but it is
the first example of a oneway method, so the capidl documentation
backend didn't handle it yet (with the result that it was silently
dropped).

That issue is now fixed, and the document online should update shortly.

> 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.

shap