pcp
[Top] [All Lists]

Re: [pcp] pcp updates: libpcp_json

To: Nathan Scott <nathans@xxxxxxxxxx>
Subject: Re: [pcp] pcp updates: libpcp_json
From: Lukas Berk <lberk@xxxxxxxxxx>
Date: Fri, 29 Jul 2016 00:06:24 -0400
Cc: pcp@xxxxxxxxxxx
Delivered-to: pcp@xxxxxxxxxxx
In-reply-to: <1587241205.10398393.1469669006131.JavaMail.zimbra@xxxxxxxxxx> (Nathan Scott's message of "Wed, 27 Jul 2016 21:23:26 -0400 (EDT)")
References: <87shuvyko9.fsf@xxxxxxxxxx> <301047582.10164791.1469605756445.JavaMail.zimbra@xxxxxxxxxx> <87oa5jt0wb.fsf@xxxxxxxxxx> <1587241205.10398393.1469669006131.JavaMail.zimbra@xxxxxxxxxx>
User-agent: Gnus/5.13 (Gnus v5.13) Emacs/25.0.95 (gnu/linux)
Hi,

Nathan Scott <nathans@xxxxxxxxxx> writes:
[...]
>> Ah, good call on the debian packaging, will start looking into it.
>
> OK - its fairly straightforward, use debian/*import1* as a template if you
> want to hack on it - else, toss it over the fence to me & I'll get it
> done.

Done.

[...]
> Couple things in the back of my mind - firstly, the small http client code
> (libpcp_http) is only built statically, currently, since pmdaapache is the
> only user atm (iow no .so there yet - but we plan on more (e.g. pmdadocker)
> so now would be a good time to address that instead of adding separate deb
> packages and libs for http and json).  IOW, we could definitely include it
> in a libpcp_web.so instead of a libpcp_http.so.  Then there may be a need
> for things like a little URL parsing routine, maybe parts of pmwebd could
> be made into APIs for other web servers (Apache module?) someday ... those
> are the kinds of possibilities that are making me wonder, anyway.

Ah, I didn't realize that it wasn't already packaged, in that case, I've
renamed libpcp_json to libpcp_web and thrown the latest changes in my
(now poorly named) libpcp_json branch.

I still have to work on the QA as you mentioned in the earlier thread,
will get to that asap next week.

Cheers,

Lukas

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