Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > linux.kernel > #1636317

RE: Question about SOCK_SEQPACKET

Show all headers | View raw

From: Steven Whitehouse
> Sent: 05 May 2017 11:34
...
> Just before the part that you've quoted, the description for
> SOCK_SEQPACKET says:
> "The SOCK_SEQPACKET socket type is similar to the SOCK_STREAM type, and
> is also connection-oriented. The only difference between these types is
> that record boundaries are maintained using the SOCK_SEQPACKET type. A
> record can be sent using one or more output operations and received
> using one or more input operations, but a single operation never
> transfers parts of more than one record."

Right SOCK_SEQPACKET is for protocols like ISO transport.
There is no limit on the length of a 'record'.
I've written file transfer programs that put the entire file
data into a single 'record'. The receiver disconnected on
receipt of the 'end of record'.

The socket man pages could easily be wrong - they are very IP-centric.
Remember ISO transport use declined when Unix became more popular
back in the mid 1980s. Unix sockets have never really been used for
it - the address information needed just doesn't match that IP
(especially IPv4).

	David

Back to linux.kernel | Previous | Next — Previous in thread | Find similar | Unroll thread

Thread

Question about SOCK_SEQPACKET Sam Kumar <samkumar99@gmail.com> - 2017-05-05 07:20 +0200
  Re: Question about SOCK_SEQPACKET Steven Whitehouse <swhiteho@redhat.com> - 2017-05-05 11:50 +0200
    Re: Question about SOCK_SEQPACKET Sowmini Varadhan <sowmini.varadhan@oracle.com> - 2017-05-05 12:20 +0200
      Re: Question about SOCK_SEQPACKET Steven Whitehouse <swhiteho@redhat.com> - 2017-05-05 12:40 +0200
        RE: Question about SOCK_SEQPACKET David Laight <David.Laight@ACULAB.COM> - 2017-05-05 13:30 +0200

csiph-web