Re: [9fans] adding TCP half-duplex close

2017-02-04 Thread Skip Tavakkolian
that makes sense. thanks. On Sat, Feb 4, 2017 at 5:38 AM Charles Forsyth wrote: > > On 4 February 2017 at 01:56, Skip Tavakkolian > wrote: > > Shutting down the write-end (i.e. 'shut_wr'), should send FIN, and > transition to Finwait1. > >

Re: [9fans] adding TCP half-duplex close

2017-02-04 Thread Skip Tavakkolian
yes, i'm still trying to find a real situation where this would be critical. i asked go-nuts list for production examples at the same time as the start of this thread. no answers yet. On Sat, Feb 4, 2017 at 3:31 AM Charles Forsyth wrote: > it's also funny that the

Re: [9fans] adding TCP half-duplex close

2017-02-04 Thread Fran. J Ballesteros
I used half closes to put go chans in the network for my weird chan based network calls. But the code works without such feature. Being just that, I dont know if it counts. > El 5 feb 2017, a las 5:39, Skip Tavakkolian > escribió: > > yes, i'm still trying to

Re: [9fans] adding TCP half-duplex close

2017-02-04 Thread Skip Tavakkolian
cool. On Fri, Feb 3, 2017 at 10:35 PM Bakul Shah wrote: > For the shut_rd case, I think a cleaner impl is to send RST *only* if > there is pending data (received but not read by the user) or new data is > received after the read end is closed. At the moment I don't recall

Re: [9fans] adding TCP half-duplex close

2017-02-04 Thread Bakul Shah
I think shutdown(sock, SHU_RD) is mainly to let the sender generate an SIGPIPE signal in case it has sent data on a closed direction of a connection. But I think this is only for completeness. Almost always you’d use close(sock). At least I have not found a usecase when I’d want to shutdown the

Re: [9fans] adding TCP half-duplex close

2017-02-04 Thread Charles Forsyth
On 4 February 2017 at 01:56, Skip Tavakkolian wrote: > Shutting down the write-end (i.e. 'shut_wr'), should send FIN, and > transition to Finwait1. i'd make it a "read" or "write" parameter to the existing "hangup" message. older implementations that don't accept

Re: [9fans] adding TCP half-duplex close

2017-02-04 Thread Charles Forsyth
I did once have a use for this in an o/s of mine, in a sort of network pipe to servers, but it was so variably implemented by other systems (data was flushed, or not) I gave it up as not particularly useful in practice, except between two known systems that did what you wanted. On 4 February 2017

Re: [9fans] adding TCP half-duplex close

2017-02-04 Thread Charles Forsyth
it's also funny that the rationale seems to be to pass the same conformance test for Go that once had it added to Inferno so it would pass a Java test but it was never otherwise used for reasons already given, so I took it out again. On 4 February 2017 at 10:11, Charles Forsyth