8146298: (dc spec) connect and disconnect methods should specify that they may block

Alan Bateman Alan.Bateman at oracle.com
Wed Nov 13 17:01:24 UTC 2019



On 13/11/2019 16:25, Brian Burkhalter wrote:
>
> How about changing the first paragraph of the connect() doc to this:
>
>    * <p> The channel's socket is configured so that it only receives
>   * datagrams from, and sends datagrams to, the given remote <i>peer</i>
>   * address.  Once connected, datagrams may not be received from or 
> sent to
>   * any other address.  Datagrams in the channel's {@link
>   * java.net.StandardSocketOptions#SO_RCVBUF socket receive buffer}, which
>   * have not been {@link #receive(ByteBuffer) received} before 
> invoking this
>   * method, may be discarded.  The channel's socket remains connected 
> until
>   * it is explicitly disconnected or until it is closed.
>
> Having “which have not been received” as the text of a @link ends up 
> producing what looks like one big link due to consecutive @links so I 
> only have “received” as a link.
>
The wording looks good.

-Alan

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://mail.openjdk.java.net/pipermail/nio-dev/attachments/20191113/93327ddc/attachment.html>


More information about the nio-dev mailing list