kenj wrote:
> [...]
> OK Frank, brace yourself for some ancient history ...
Awesome, thanks.
> [...]
> As a result curr_pmns is serving multiple purposes
> - _the_ PMNS for pmcd
> - _the_ PMNS for local contexts
> - _the_ PMNS for all host contexts if pmLoadNameSpace() is explicitly
> called
> [...]
> I know this is a convoluted answer, the short verion is that for all
> "normal" (tm) uses, there is one PMNS per context.
OK, I wonder whether my hypothetical usage is normal (tm) for your
purposes. For pmwebapi, the program may have a motley crew of pmapi
contexts open concurrently, some local, some to various remote pmcds,
some to local sundry archives.
Periodically, it'd like to run pmTraversePMNS_r to enumerate the
namespace associated with a particular context. But said function
doesn't take the context as a parameter. So which PMNS would it
choose from its stable of possible alternatives?
- FChE
|