| To: | "nathans@xxxxxxxxxx" <nathans@xxxxxxxxxx> |
|---|---|
| Subject: | Re: [pcp] PCP question ... leading to pmimport discussion |
| From: | Greg Banks <gnb@xxxxxxxxxxx> |
| Date: | Wed, 23 Jun 2010 14:49:34 +1000 |
| Cc: | "pmatousu@xxxxxxxxxxxxx" <pmatousu@xxxxxxxxxxxxx>, "kenj@xxxxxxxxxxxxxxxx" <kenj@xxxxxxxxxxxxxxxx>, "pcp@xxxxxxxxxxx" <pcp@xxxxxxxxxxx> |
| In-reply-to: | <79179398.209531277247128966.JavaMail.root@xxxxxxxxxxxxxxxxxx> |
| References: | <79179398.209531277247128966.JavaMail.root@xxxxxxxxxxxxxxxxxx> |
| User-agent: | Thunderbird 2.0.0.23 (X11/20090817) |
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 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. -- Greg. |
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | Re: [pcp] PCP question ... leading to pmimport discussion, Nathan Scott |
|---|---|
| Next by Date: | Re: [pcp] PCP question ... leading to pmimport discussion, Petr MatouÅÅ |
| Previous by Thread: | Re: [pcp] PCP question ... leading to pmimport discussion, nathans |
| Next by Thread: | Re: [pcp] PCP question ... leading to pmimport discussion, Nathan Scott |
| Indexes: | [Date] [Thread] [Top] [All Lists] |