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

Groups > linux.kernel > #1379396

Re: [PATCH 1/3] rxrpc: Don't permit use of connect() op and simplify sendmsg() op

Show all headers | View raw

From: David Howells <dhowells@redhat.com>
Date: Tue, 12 Apr 2016 16:05:41 +0100

> Simplify the RxRPC user interface and remove the use of connect() to direct
> client calls.  It is redundant given that sendmsg() can be given the target
> address and calls to multiple targets are permitted from a client socket
> and also from a service socket.

You can't just change completely the socket semantics for your
protocol like this, every single userland application is going to
break.

Sorry, there is no way I am applying changes like this.

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

Thread

[PATCH 0/3] RxRPC: 2nd rewrite part 2 David Howells <dhowells@redhat.com> - 2016-04-12 17:10 +0200
  [PATCH 2/3] rxrpc: The RXRPC_ACCEPT control message should not have  an address David Howells <dhowells@redhat.com> - 2016-04-12 17:10 +0200
  [PATCH 1/3] rxrpc: Don't permit use of connect() op and simplify  sendmsg() op David Howells <dhowells@redhat.com> - 2016-04-12 17:10 +0200
    Re: [PATCH 1/3] rxrpc: Don't permit use of connect() op and  simplify sendmsg() op David Miller <davem@davemloft.net> - 2016-04-15 03:10 +0200
      Re: [PATCH 1/3] rxrpc: Don't permit use of connect() op and simplify sendmsg() op David Howells <dhowells@redhat.com> - 2016-04-15 05:30 +0200

csiph-web