pcp
[Top] [All Lists]

Re: [pcp] __pmDiscoverServicesWithOptions() error codes

To: Dave Brolley <brolley@xxxxxxxxxx>
Subject: Re: [pcp] __pmDiscoverServicesWithOptions() error codes
From: Nathan Scott <nathans@xxxxxxxxxx>
Date: Tue, 16 Sep 2014 04:56:33 -0400 (EDT)
Cc: PCP Mailing List <pcp@xxxxxxxxxxx>
Delivered-to: pcp@xxxxxxxxxxx
In-reply-to: <54173329.7030701@xxxxxxxxxx>
References: <54173329.7030701@xxxxxxxxxx>
Reply-to: Nathan Scott <nathans@xxxxxxxxxx>
Thread-index: 8el3zZhPYVQAvzA7ihqcjfLG8y6rjw==
Thread-topic: __pmDiscoverServicesWithOptions() error codes
Hi Dave,

----- Original Message -----
> The following address RHBZ 1139529 and update the pmdiscoverservices(3)
> man page which had fallen behind.
> 
> __pmDiscoverServicesWithOptions was left as a __-prefixed API because we
> were unsure of the direction it was going. It's additional functionality
> remains undocumented. Is it appropriate to document it in
> pmdiscoverservices(3) 

Absolutely.  See pmGetConfig(3) for a similar sort of situation.

> Or perhaps it's time to
> remove the __ prefix and make it into a full fledged pmapi API?

To me, seems too soon (one/two releases only?).  I'd like to see more
time - more use of the API from client tools, see if it stands up to
more discovery types below the API too, that sort of thing.  And if
none of these things come along over the next few months to help set
our direction then yep, sure, let's push it up to PMAPI level as-is.

cheers.

--
Nathan

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