Skip to content

Commit

Permalink
Publisher need not be a member of a custom range
Browse files Browse the repository at this point in the history
Signed-off-by: David Solt <[email protected]>
  • Loading branch information
dsolt committed Jul 14, 2022
1 parent c9a1a18 commit de8c3be
Showing 1 changed file with 7 additions and 8 deletions.
15 changes: 7 additions & 8 deletions Chap_API_Publish.tex
Original file line number Diff line number Diff line change
Expand Up @@ -76,9 +76,9 @@ \section{\code{PMIx_Publish}}
ranges. Custom ranges are consider different if they have different members.
Duplicate keys being published on the same data range shall return the
\refconst{PMIX_ERR_DUPLICATE_KEY} error.
publishing to a \declareconstitem{PMIX_RANGE_CUSTOM}
publishing to a \refconst{PMIX_RANGE_CUSTOM}
range which does not include the publisher will prevent
any processes from using \refapi{PMIX_Lookup} to access the published data.
any processes from using \refapi{PMIx_Lookup} to access the published data.

In some cases, implementations may be incapable of distinguishing which
info keys in the \refarg{info} array are for publishing and which info keys are
Expand Down Expand Up @@ -376,9 +376,9 @@ \section{\code{PMIx_Lookup}}
\descr

Lookup information published by a process or host environment using \refapi{PMIx_Publish} or \refapi{PMIx_Publish_nb}.
A lookup operation is always performed on a range which can be specified using the directive \refconst{PMIX_RANGE} or otherwise defaults to \refconst{PMIX_RANGE_SESSION}.
The lookup operation will be constrained to publishers that fall within
the range and that published data to the range.
A lookup operation is always performed on a range which can be specified using the directive \refAttributeItem{PMIX_RANGE} or otherwise defaults to \refconst{PMIX_RANGE_SESSION}.

The lookup operation will be constrained to data published to the specified range.
Data is returned per the retrieval rules of Section \ref{chap:pub:retrules}.

The \argref{data} parameter consists of an array of \refstruct{pmix_pdata_t} structures with the keys specifying the requested information.
Expand Down Expand Up @@ -600,9 +600,8 @@ \section{Retrieval rules for published data}
\begin{enumerate}
\item The lookup key matches the published key.
\item The type of range specified by the publisher is the same as the type of range specified by the requester.
\item If a custom range is specified by the publisher and the requester, the members described in both cases must be identical.
\item The publisher must be a member of the requestors range.
\item The requestor must be a member of the publishers range.
\item If a custom range is specified by the publisher and the requester, the members described in both cases must be identical. The publisher is not required to be a member of a custom range.
\item The requestor must be a member of the publisher's range.

%%option2:
%%
Expand Down

0 comments on commit de8c3be

Please sign in to comment.