| To: | "Frank Ch. Eigler" <fche@xxxxxxxxxx> |
|---|---|
| Subject: | Re: pcp updates - yippee secure socket connections work |
| From: | Ken McDonell <kenj@xxxxxxxxxxxxxxxx> |
| Date: | Sat, 20 Apr 2013 06:27:02 +1000 |
| Cc: | pcp@xxxxxxxxxxx |
| Delivered-to: | pcp@xxxxxxxxxxx |
| In-reply-to: | <20130419141647.GC8308@xxxxxxxxxx> |
| References: | <516F8AB8.6000807@xxxxxxxxxxxxxxxx> <y0md2trfkab.fsf@xxxxxxxx> <5170B8D3.9000305@xxxxxxxxxxxxxxxx> <20130419141647.GC8308@xxxxxxxxxx> |
| User-agent: | Mozilla/5.0 (X11; Linux i686; rv:17.0) Gecko/20130329 Thunderbird/17.0.5 |
On 20/04/13 00:16, Frank Ch. Eigler wrote: ... Note that even the TIMEOUT_DEFAULT is a problem in that allows a naughty client to send one byte on channel, and lets pmcd sit there for a few seconds waiting for more, not servicing anyone else. This is what a further rework inspired by the "continuation passing style" comment in pduread() could correct. Point taken ... but that involves much more work as pduread() would need to have one non-blocking behaviour for pmcd (and mainloop changes to pmcd) and "classical" behaviour for everyone else as almost every application we build as part of pcp or pcp-gui uses this routine indirectly through __pmGetPDU(). Is someone keeping a wishlist / backlog of work items we agree should be done at some point in the future? |
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | Re: [pcp-announce] [pcp] Bugfix updates for PCP and PCP GUI released, Nathan Scott |
|---|---|
| Next by Date: | Processing of pcp-gui_1.5.8_i386.changes, Debian FTP Masters |
| Previous by Thread: | Re: pcp updates - yippee secure socket connections work, Frank Ch. Eigler |
| Next by Thread: | Re: pcp updates - yippee secure socket connections work, Frank Ch. Eigler |
| Indexes: | [Date] [Thread] [Top] [All Lists] |