You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: README.md
+4-3Lines changed: 4 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -4,7 +4,8 @@ WebSocket frame parser
4
4
5
5
### Features
6
6
* No dependencies
7
-
* Works with chunks of a data - no need to buffer the whole request
7
+
* No internal buffering
8
+
* No need to buffer the whole frame — works with chunks of a data
8
9
9
10
This is a parser for WebSocket frame-messages written in C (by [RFC6455](https://tools.ietf.org/html/rfc6455)).
10
11
It does not make any syscalls nor allocations, it does not
@@ -33,8 +34,8 @@ These functions must match the signatures defined in the websocket-parser header
33
34
34
35
Returning a value other than 0 from the callbacks will abort message processing.
35
36
36
-
Initialize the `struct` using `http_parser_init()` and set the callbacks. That might look something
37
-
like this for a request parser:
37
+
One websocket_parser object is used per TCP connection. Initialize `websocket_parser` struct using `http_parser_init()` and set the callbacks. That might look something
0 commit comments