diff options
| author | Alex Trotsenko <alex1973tr@gmail.com> | 2016-07-29 19:15:48 +0300 |
|---|---|---|
| committer | Alex Trotsenko <alex1973tr@gmail.com> | 2016-08-02 10:03:45 +0000 |
| commit | fcbbd7bc3d1f7ba9dc2dec1dc3222d0b63660ba5 (patch) | |
| tree | 5bad15eae420181eead0d97b2a4b11c5ac861053 /src/network/socket/qsctpsocket.cpp | |
| parent | d875d5e2fc66b9a4ab1afea8441b33d4afc6e9b5 (diff) | |
Fix grammar issues in SCTP documentation
Change-Id: I11bfb20dc3d4db98dccfd3bc680fb1ffbd522508
Reviewed-by: Thiago Macieira <thiago.macieira@intel.com>
Reviewed-by: Edward Welbourne <edward.welbourne@qt.io>
Diffstat (limited to 'src/network/socket/qsctpsocket.cpp')
| -rw-r--r-- | src/network/socket/qsctpsocket.cpp | 18 |
1 files changed, 9 insertions, 9 deletions
diff --git a/src/network/socket/qsctpsocket.cpp b/src/network/socket/qsctpsocket.cpp index dcfd6806a4..9ab241f9ab 100644 --- a/src/network/socket/qsctpsocket.cpp +++ b/src/network/socket/qsctpsocket.cpp @@ -60,7 +60,7 @@ independent channels, so that if there is data loss in one stream, delivery will not be affected for the other streams. - As message-oriented, SCTP transports a sequence of messages, + Being message-oriented, SCTP transports a sequence of messages, rather than transporting an unbroken stream of bytes as does TCP. Like in UDP, in SCTP a sender sends a message in one operation, and that exact message is passed to the receiving application @@ -83,17 +83,17 @@ \endlist To set a continuous byte stream mode, instantiate QSctpSocket and - call setMaxChannelCount() with the negative number of channels. This - gives the ability to use QSctpSocket as a regular buffered - QTcpSocket. You can call connectToHost() to initiate connection - with endpoint, write() to transmit and read() to receive data from - the peer, but you cannot distinguish message boundaries. + call setMaxChannelCount() with a negative value. This gives the + ability to use QSctpSocket as a regular buffered QTcpSocket. You + can call connectToHost() to initiate connection with endpoint, + write() to transmit and read() to receive data from the peer, but + you cannot distinguish message boundaries. By default, QSctpSocket operates in datagram mode. Before connecting, call setMaxChannelCount() to set the maximum number of channels that the application is prepared to support. This number - is a negotiated parameter with remote endpoint and its value can - be bounded by the operating system. The default value of 0 + is a parameter negotiated with the remote endpoint and its value + can be bounded by the operating system. The default value of 0 indicates to use the peer's value. If both endpoints have default values, then number of connection channels is system-dependent. After establishing a connection, you can fetch the actual number @@ -412,7 +412,7 @@ void QSctpSocket::disconnectFromHost() is 0, endpoint's value for maximum number of channels is used. Negative \a count sets a continuous byte stream mode. - Call this member only when QSctpSocket is in UnconnectedState. + Call this method only when QSctpSocket is in UnconnectedState. \sa maxChannelCount(), readChannelCount(), writeChannelCount() */ |