On Fri, Oct 02, 2009 at 02:45:21PM -0700, Ben Laurie 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.
>
> Ah, I see. Hmmm.
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.
-- Jacob
--~--~---------~--~----~------------~-------~--~----~
Chromium Developers mailing list: [email protected]
View archives, change email options, or unsubscribe:
http://groups.google.com/group/chromium-dev
-~----------~----~----~----~------~----~------~--~---
