forked from quic-go/quic-go
fix documentation for ConnectionState.SupportsDatagrams (#4754)
Support for QUIC datagrams (RFC 9221) is a unilateral declaration.
This commit is contained in:
@@ -98,7 +98,6 @@ type ReceiveStream interface {
|
|||||||
// SetReadDeadline sets the deadline for future Read calls and
|
// SetReadDeadline sets the deadline for future Read calls and
|
||||||
// any currently-blocked Read call.
|
// any currently-blocked Read call.
|
||||||
// A zero value for t means Read will not time out.
|
// A zero value for t means Read will not time out.
|
||||||
|
|
||||||
SetReadDeadline(t time.Time) error
|
SetReadDeadline(t time.Time) error
|
||||||
}
|
}
|
||||||
|
|
||||||
@@ -357,10 +356,10 @@ type ClientHelloInfo struct {
|
|||||||
type ConnectionState struct {
|
type ConnectionState struct {
|
||||||
// TLS contains information about the TLS connection state, incl. the tls.ConnectionState.
|
// TLS contains information about the TLS connection state, incl. the tls.ConnectionState.
|
||||||
TLS tls.ConnectionState
|
TLS tls.ConnectionState
|
||||||
// SupportsDatagrams says if support for QUIC datagrams (RFC 9221) was negotiated.
|
// SupportsDatagrams indicates whether the peer advertised support for QUIC datagrams (RFC 9221).
|
||||||
// This requires both nodes to support and enable the datagram extensions (via Config.EnableDatagrams).
|
// When true, datagrams can be sent using the Connection's SendDatagram method.
|
||||||
// If datagram support was negotiated, datagrams can be sent and received using the
|
// This is a unilateral declaration by the peer - receiving datagrams is only possible if
|
||||||
// SendDatagram and ReceiveDatagram methods on the Connection.
|
// datagram support was enabled locally via Config.EnableDatagrams.
|
||||||
SupportsDatagrams bool
|
SupportsDatagrams bool
|
||||||
// Used0RTT says if 0-RTT resumption was used.
|
// Used0RTT says if 0-RTT resumption was used.
|
||||||
Used0RTT bool
|
Used0RTT bool
|
||||||
|
|||||||
Reference in New Issue
Block a user