From fe6dd5051a9e2dbf699a334f66e61e4354673b60 Mon Sep 17 00:00:00 2001 From: David Solt Date: Thu, 14 Jul 2022 11:17:23 -0500 Subject: [PATCH] Publisher does not have to be a member of custom range it is publishing to --- Chap_API_Publish.tex | 15 +++++++-------- 1 file changed, 7 insertions(+), 8 deletions(-) diff --git a/Chap_API_Publish.tex b/Chap_API_Publish.tex index 40c9d890..d84712fd 100644 --- a/Chap_API_Publish.tex +++ b/Chap_API_Publish.tex @@ -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 @@ -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. @@ -586,9 +586,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: %%