pcp
[Top] [All Lists]

Re: PCP Updates: Active Probing for __pmDiscoverServices() / pmfind

To: Dave Brolley <brolley@xxxxxxxxxx>
Subject: Re: PCP Updates: Active Probing for __pmDiscoverServices() / pmfind
From: fche@xxxxxxxxxx (Frank Ch. Eigler)
Date: Thu, 22 May 2014 17:04:12 -0400
Cc: Nathan Scott <nathans@xxxxxxxxxx>, pcp@xxxxxxxxxxx
Delivered-to: pcp@xxxxxxxxxxx
In-reply-to: <537E59F3.7070308@xxxxxxxxxx> (Dave Brolley's message of "Thu, 22 May 2014 16:11:31 -0400")
References: <5373D0D2.5090902@xxxxxxxxxx> <537CC777.3040900@xxxxxxxxxx> <399575684.12526040.1400750511921.JavaMail.zimbra@xxxxxxxxxx> <537E59F3.7070308@xxxxxxxxxx>
User-agent: Gnus/5.1008 (Gnus v5.10.8) Emacs/21.4 (gnu/linux)
brolley wrote:

> [...]  As part of this, I'm seeing some duplicate code in various
> parts of PCP for extracting port numbers from environment
> variables. I'm going to take a shot at consolidating this into a new
> libpcp API.

For what it's worth, I am a little uneasy at the sheer number of
general utility functions that have collected in the PCP API (in the
forms of exported symbols in the .so's) that are unrelated to the core
pcp mission of documented or even exampled PMAPI.

Perhaps we should take a closer look at the idea in [1], wherein we'd
gradually build up libpcputil .a (not .so) type utility libraries for
reuse by in-tree tools, but specifically not documented/available for
use by out-of-tree PMAPI programs.  We could throw the impl.h
etc. kitchen sink in there, and not worry about ABI or API stability.

[1] http://oss.sgi.com/pipermail/pcp/2014-April/004751.html


- FChE

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