Rename WebSocketDataCallback's frame param from opcode to bits

[heshammahamed]

The parameter was named opcode, but civetweb actually passes the raw first byte of the WebSocket frame header (FIN flag + reserved bits + the real opcode packed into the low 4 bits), not the opcode alone. Renamed to bits to match civetweb's own naming, and updated the docs (EN + AR) and examples to match this correct understanding.

[sarmadka]

Where did you get that info about Civetweb from, and is their documentation wrong? In their documentation the mg_websocket_data_handler function type has the second param named opcode.
https://github.com/civetweb/civetweb/blob/master/docs/api/mg_set_websocket_handler.md

[heshammahamed]

I think this is a problem in their Docs.

this is from civetweb's own header :

mg_websocket_data_handler
Is called when a data frame has been received from the client.
Parameters:
bits: first byte of the websocket frame, see websocket RFC at
http://tools.ietf.org/html/rfc6455, section 5.2
data, data_len: payload, with mask (if any) already applied.
Return value:
1: keep this websocket connection open.
0: close this websocket connection.

search on it in this file to make sure : https://github.com/civetweb/civetweb/blob/master/include/civetweb.h