Lines Matching +full:- +full:- +full:disable +full:- +full:telnet

1 <!--
4 SPDX-License-Identifier: curl
5 -->
41  `CURLOPT_WS_OPTIONS` - to control specific behavior. `CURLWS_RAW_MODE` makes
46  `curl_ws_recv()` - receive a WebSocket frame
48  `curl_ws_send()` - send a WebSocket frame
50  `curl_ws_meta()` - return WebSocket metadata within a write callback
66 HTTP server - the transfer returns `CURLE_HTTP_RETURNED_ERROR` for that
77 - This server is already integrated and working in the test suite
79 - We want maximum control and ability to generate broken protocol and negative
85 The plan is to make curl do WebSocket similar to telnet/nc. That part of the
90  - Read stdin and send off as messages. Consider newline as end of fragment.
92  - Respond to PINGs automatically
93  - Issue PINGs at some default interval (option to switch off/change interval?)
94  - Allow `-d` to specify (initial) data to send (should the format allow for
96  - Exit after N messages received, where N can be zero.
100 - Verify the Sec-WebSocket-Accept response. It requires a sha-1 function.
101 - Verify Sec-WebSocket-Extensions and Sec-WebSocket-Protocol in the response
102 - Make WebSocket work with hyper
103 - Consider a `curl_ws_poll()`
104 - Make sure WebSocket code paths are fuzzed
105 - Add client-side PING interval
106 - Provide option to disable PING-PONG automation
107 - Support compression (`CURLWS_COMPRESS`)
118 - doxygen generated docs only makes them hard to navigate. No tutorial, no
121 - seems (too) tightly integrated with a specific TLS library, while we want to
125 - seems (too) tightly integrated with event libraries
127 - the references to threads and thread-pools in code and APIs indicate too
130 - "bloated" - it is a *huge* library that is actually more lines of code than
133 - WebSocket is a fairly simple protocol on the network/framing layer so