Replies: 1 comment 2 replies
-
|
https://sookocheff.com/post/networking/how-do-websockets-work/ WebSockets begin life as a standard HTTP request and response. Within that request response chain, the client asks to open a WebSocket connection, and the server responds (if its able to). If this initial handshake is successful, the client and server have agreed to use the existing TCP/IP connection that was established for the HTTP request as a WebSocket connection. Data can now flow over this connection using a basic framed message protocol. Once both parties acknowledge that the WebSocket connection should be closed, the TCP connection is torn down. |
Beta Was this translation helpful? Give feedback.
2 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
I have cloned the repository and aim to establish a WebSocket server to facilitate communication and control with a standby client station using the OCPP protocol. The WebSocket connection should follow the format
ws://[server_ip]:[port]/ocpp/[chargepoint_identity].Upon reviewing the codebase, I noticed that only HTTP URL configurations are implemented. Could you provide guidance or code modifications to establish a WebSocket server compatible with the OCPP protocol for the specified URL format?
Specifically, I need assistance in setting up the WebSocket server to handle connections and manage communication with the client using the provided WebSocket URL structure.
Beta Was this translation helpful? Give feedback.
All reactions