Has TLS options logic and is used to do get requests and to setup the Websocket in grisp_seawater_client
The get function is not used in our API which is 100% websocket based.
grisp_seawater_client
The connect function is blocking the caller and contains multiple steps.
The upgrade function uses explicit receive, which is un-necessary since we are in gen_server.
The ws state is not tracked and if the board it's disconnected, api calls crash.
New option
ws_request_timeout (default = 5_000) allows to controll the timeout of each API requerst going through the WS.
The option is now documented in the README.md
Details addressed in the PR
grisp_seawater_http
grisp_seawater_clientgetfunction is not used in our API which is 100% websocket based.grisp_seawater_client
connectfunction is blocking the caller and contains multiple steps.upgradefunction uses explicitreceive, which is un-necessary since we are ingen_server.New option
ws_request_timeout(default = 5_000) allows to controll the timeout of each API requerst going through the WS. The option is now documented in the README.md