| To: | "Frank Ch. Eigler" <fche@xxxxxxxxxx>, pcp developers <pcp@xxxxxxxxxxx> |
|---|---|
| Subject: | Re: [pcp] PMAPI observations re. converting an app to pcp |
| From: | Martins Innus <minnus@xxxxxxxxxxx> |
| Date: | Fri, 26 Sep 2014 11:35:48 -0400 |
| Delivered-to: | pcp@xxxxxxxxxxx |
| In-reply-to: | <20140925180407.GA18679@xxxxxxxxxx> |
| References: | <20140925180407.GA18679@xxxxxxxxxx> |
| User-agent: | Mozilla/5.0 (Macintosh; Intel Mac OS X 10.9; rv:24.0) Gecko/20100101 Thunderbird/24.6.0 |
Frank, - The API is really wordy for basic tasks such as extracting and scaling some metrics. It takes several setup steps, several arrays of data, several error-prone array/pointer arithmetic, with error-handling at each step. It adds up to way too much code - it's >100 lines, and not done yet. We need a higher level API that combines the lookup/indom/fetch/extract/scale steps (doing internal caching/lookups as necessary), with the goal of making it easy to interface with an enclosing application. From my perspective, this would be very useful. It would be great to have something higher level that was easy to use for quick one-off applications. Thanks Martins |
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | Re: PCP trees for web and middleware development, Frank Ch. Eigler |
|---|---|
| Next by Date: | Re: PCP trees for web and middleware development, Frank Ch. Eigler |
| Previous by Thread: | Re: [pcp] PMAPI observations re. converting an app to pcp, Frank Ch. Eigler |
| Next by Thread: | Re: [pcp] PMAPI observations re. converting an app to pcp, Nathan Scott |
| Indexes: | [Date] [Thread] [Top] [All Lists] |