On Fri, Oct 2, 2009 at 3:44 PM, Jacob Mandelson <[email protected]> wrote: >> > 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. > > The Linux send(2) man page explicitly says the message is all-or-nothing, > and the SUS entry seems to indicate the same thing, though not as > clearly, so that framing protocol can probably just be [<length><data>]* > Still more complicated than having the socket layer do it though.
And SOCK_SEQPACKET is atomic, but simulating it with <length><data> isn't, so the simulation might break down with multiple concurrent writers. --~--~---------~--~----~------------~-------~--~----~ Chromium Developers mailing list: [email protected] View archives, change email options, or unsubscribe: http://groups.google.com/group/chromium-dev -~----------~----~----~----~------~----~------~--~---
