pcp
[Top] [All Lists]

Re: [pcp] pcp updates - yippee secure socket connections work

To: Ken McDonell <kenj@xxxxxxxxxxxxxxxx>
Subject: Re: [pcp] pcp updates - yippee secure socket connections work
From: Nathan Scott <nathans@xxxxxxxxxx>
Date: Fri, 19 Apr 2013 00:04:30 -0400 (EDT)
Cc: "Frank Ch. Eigler" <fche@xxxxxxxxxx>, pcp@xxxxxxxxxxx
Delivered-to: pcp@xxxxxxxxxxx
In-reply-to: <5170B8D3.9000305@xxxxxxxxxxxxxxxx>
References: <516F8AB8.6000807@xxxxxxxxxxxxxxxx> <y0md2trfkab.fsf@xxxxxxxx> <5170B8D3.9000305@xxxxxxxxxxxxxxxx>
Reply-to: Nathan Scott <nathans@xxxxxxxxxx>
Thread-index: Wckn+QuOV4Ahg7osqoJCkmV+3vqITQ==
Thread-topic: pcp updates - yippee secure socket connections work

----- Original Message -----
> ...
> Note that noone (outside some qa apps) uses TIMEOUT_ASYNC nor its evil
> twin GETPDU_ASYNC thanks to this piece of impl.h obscurity
> #define GETPDU_ASYNC     TIMEOUT_ASYNC   /* backward-compatibility */
> ... I suspect both are Neanderthal throwbacks to the async PDU stuff
> that I ripped out of libpcp when I did the thread-safe work ... I've put
> pulling these on my TODO list, and this would make pduread() much simpler.

I've done this code removal already, testing it now & planning to put it
into this release.  The pmproxy & pmtrace changes I'd prefer to defer to
next release if that's OK.

cheers.

--
Nathan

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