RFR 8043954: Fix behavior difference of connect() for AIX (original) (raw)
Jonathan Lu luchsh at linux.vnet.ibm.com
Thu Jun 5 10:37:30 UTC 2014
- Previous message: RFR 8043954: Fix behavior difference of connect() for AIX
- Next message: RFR 8043954: Fix behavior difference of connect() for AIX
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Hi Alan,
On Wed, Jun 4, 2014 at 9:16 PM, Alan Bateman <Alan.Bateman at oracle.com> wrote:
On 04/06/2014 07:31, Jonathan Lu wrote:
Hi Volker,
Thanks for your comment! an updated webrev was made at http://cr.openjdk.java.net/~luchsh/JDK-8043954.2/ Would it make sense to set errno to sockoptarg for the case that getsockopt(SOERROR) returns an error? Otherwise it looks okay to me.
If getsockopt(SO_ERROR) failed, I did not find any explicit docs about the behavior. but as I tested with some C code snippet, the value of sockopt_arg would not be changed if getsockopt(SO_ERROR) failed. So I prefer to keep the current approach, does it make sense to you ?
-Alan.
Many thanks Jonathan
- Previous message: RFR 8043954: Fix behavior difference of connect() for AIX
- Next message: RFR 8043954: Fix behavior difference of connect() for AIX
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]