Re: [pcp] Archive discovery, was Re: __pmDiscoverServices()/pmfind Enhancements

[Dave Brolley <brolley@xxxxxxxxxx>]

On 05/22/2014 09:53 AM, Frank Ch. Eigler wrote:
> > Hmm, above suggests we should've thought of an "options" parameter
> > to pmDiscoverServices(3).  [...]
> One benefit of keeping options textual and similar is for their direct
> transposition to a user interface like a config file or a pmfind
> command line argument.  Sure, one could create some enum tuple widget
> like ... __pmOptions (?), but then it needs to just hop between ascii
> or multiple flags elsewhere anyway, with much more complexity.  (Or
> did you simply imagine adding another 'char* options' parameter to
> the discover api?)
I also like the idea of textual options. It makes it easy to extend the 
API without changing the ABI. Some options would be global, like the 
proposed timeout while others would be mechanism-specific, like the 
currently proposed maxThreads for active probing (although this could 
conceivably also be a global option).
I like the idea of the mechanism-specific options remaining with the 
mechanism string. I would not object to an additional global options 
string. I had thought about it but thought that it was too late to add it.
Dave