pcp
[Top] [All Lists]

Re: PMNS scope globality

To: "Frank Ch. Eigler" <fche@xxxxxxxxxx>
Subject: Re: PMNS scope globality
From: Ken McDonell <kenj@xxxxxxxxxxxxxxxx>
Date: Fri, 06 Apr 2012 06:45:35 +1000
Cc: pcp developers <pcp@xxxxxxxxxxx>
In-reply-to: <y0mobr69lr2.fsf@xxxxxxxx>
References: <20120404202551.GA29020@xxxxxxxxxx> <1333584398.2439.13.camel@xxxxxxxxxxxxxxxxxxxxxxx> <y0mobr69lr2.fsf@xxxxxxxx>
On Thu, 2012-04-05 at 12:38 -0400, Frank Ch. Eigler wrote:
> ...
> 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.

This usage would not be historically normal (except for on infamous
product at SGI), but is supported.

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

Finally, a simple answer ... the current context defines the PMNS to be
used ... 8^)>


<Prev in Thread] Current Thread [Next in Thread>