On Wed, Oct 7, 2009 at 8:09 PM, Evan Martin <[email protected]> wrote: > On Fri, Oct 2, 2009 at 2:40 PM, Adam Langley <[email protected]> wrote: >> >> On Fri, Oct 2, 2009 at 2:37 PM, Ben Laurie <[email protected]> wrote: >>> Why will it certainly not work? From what (little) I understand, >>> SOCK_SEQPACKET adds record boundaries to SOCK_STREAM ... presumably >>> one could simulate that over SOCK_STREAM? >> >> There are multiple, concurrent writers to the socket. If you make >> assumptions about the kernel's behaviour, you might be able to come up >> with a workable framing protocol, but it's much better to use the >> correct socket type. > > If anyone gets the chance, I would happily pre-LGTM a change that > stuffs some comments near this code explaining the reasoning for this.
http://codereview.chromium.org/270041 > --~--~---------~--~----~------------~-------~--~----~ Chromium Developers mailing list: [email protected] View archives, change email options, or unsubscribe: http://groups.google.com/group/chromium-dev -~----------~----~----~----~------~----~------~--~---
