<html><head></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><br><div><br class="Apple-interchange-newline"><blockquote type="cite"><div style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><div><div>On Jun 4, 2011, at 11:32 PM, Martin v. Löwis wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite"><span class="Apple-style-span" style="border-collapse: separate; font-family: 'Bitstream Vera Sans Mono'; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: 2; text-indent: 0px; text-transform: none; white-space: normal; widows: 2; word-spacing: 0px; -webkit-border-horizontal-spacing: 0px; -webkit-border-vertical-spacing: 0px; -webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px; font-size: medium; "><span class="Apple-style-span" style="font-family: monospace; ">b) telling people to use Twisted or asyncore on the server side<br> if they are new to sockets is bad advice. People *first* have<br> to understand sockets, and *then* can use these libraries<br> and frameworks. Those libraries aren't made to be black boxes<br> that work even if you don't know how - you *have* to know how<br> they work inside, or else you can't productively use them.<br></span></span></blockquote></div></div></blockquote><br></div><div>It would be fine to have a separate networking howto guide that covers</div><div>libraries, frameworks, and high level APIs, but I agree with Martin that</div><div>the Socket HOWTO needs to cover sockets. That's what a person expects</div><div>to learn when they click on the Socket HOWTO link.</div><div><br></div><div>Raymond</div><br></body></html>