| To: | Nathan Scott <nathans@xxxxxxxxxx> |
|---|---|
| Subject: | Re: [pcp] pcp updates - yippee secure socket connections work |
| From: | Ken McDonell <kenj@xxxxxxxxxxxxxxxx> |
| Date: | Fri, 19 Apr 2013 14:16:51 +1000 |
| Cc: | "Frank Ch. Eigler" <fche@xxxxxxxxxx>, pcp@xxxxxxxxxxx |
| Delivered-to: | pcp@xxxxxxxxxxx |
| In-reply-to: | <1780029987.3226532.1366344270106.JavaMail.root@xxxxxxxxxx> |
| References: | <516F8AB8.6000807@xxxxxxxxxxxxxxxx> <y0md2trfkab.fsf@xxxxxxxx> <5170B8D3.9000305@xxxxxxxxxxxxxxxx> <1780029987.3226532.1366344270106.JavaMail.root@xxxxxxxxxx> |
| User-agent: | Mozilla/5.0 (X11; Linux i686; rv:17.0) Gecko/20130329 Thunderbird/17.0.5 |
On 19/04/13 14:04, Nathan Scott wrote: ----- 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. Thanks and fine by me. I'll take a look at the pmproxy and libpcp_trace issues, but not commit anything until 3.7.2 is out the door. |
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | Re: [pcp] pcp updates - yippee secure socket connections work, Nathan Scott |
|---|---|
| Next by Date: | Re: [pcp] pmlogconf (was Re: PCP Developers Meetup notes - 17/4/2013 - 08:00-10:30 (+1000)), Nathan Scott |
| Previous by Thread: | Re: [pcp] pcp updates - yippee secure socket connections work, Nathan Scott |
| Next by Thread: | Re: pcp updates - yippee secure socket connections work, Frank Ch. Eigler |
| Indexes: | [Date] [Thread] [Top] [All Lists] |