----- "Greg Banks" <gnb@xxxxxxxxxxx> wrote:
> nathans@xxxxxxxxxx wrote:
> >
> >
> >> If there was consensus on exactly how this meta data was to be
> >> encoded in the file, then it would be possible to write a generic
> >> "csv" plugin for pmimport.
> >>
> >
> > The plan I had in mind for the pmimport tool and API was to make
> > a Perl wrapper around a plugin API so that script plugins could
> > be written.
>
> Or even better, a Perl API to generate a PCP archive programmatically,
>
> so the user can write their own main loop. I would have used such a
Yep, thats the idea - its not a massive leap to get from the current
pmimport implementation to that, AFAICT.
> thing dozens of times by now if it existed. And while you're at it,
> perhaps also a fully supported and documented C libpcp API for writing
> an archive from a C program, instead of having to do horrible things
> with __pmLogCreate() et al.
Delve further into pmimport, it does alot/all of these things (except
the fully supported/documented bit, thats an exercise for the reader).
cheers.
--
Nathan
|