Websockets in Python

WebSocket is a protocol for machine-to-machine communication that keeps a TCP connection open for bi-directional passing of information. The websocket is a connection between two computers. The connection can be used to either send or receive information from either computer. The websocket can be configured as a server or client. A websocket server listens for requests and returns a result based on the input. The server can also function as a client by sending information without a specific request.
Websockets Overview: apmonitor.com/dde/index.php/M...

[@abdullahyousef3596]

Thank you for this video, it was really helpful!

[@kylanwalters37]

Very helpful info! Thank you

[@Hallucinarix]

is there a reason you nested the uri within the function rather than an outside variable that's easier to visually identify? (say when needing to change when going from dev to production)

[@prasaddissanayake1718]

excellent

[@chenbruce318]

thanks for such comprehensive sharing!!
I have one question, are there any suggested solutions that allow me to deploy my websocket server to let external devices access it through link like wss:// ?

[@rrc]

Yes, no problem on deploying it as a web service. Just open the firewall on port 443 to not block the connection.

[@Hallucinarix]

is there a reason you nest the uri within a function rather than being declared outside as a variable that can easier be visually identified when needing to be changed? (say going from dev to production)

[@apm]

Great idea - it just adds an additional input parameter to the function, but makes the code more modular and reusable for other applications.

[@IsraelAlfaro]

Thanks so much for this video! It was very helpful. I am now wondering, how could you introduce authentication in order to connect to the websocket server? e.g. as you would with a Bearer Token when using RESTful APIs. Thanks a gain! Cheers!

[@apm]

To introduce authentication to a WebSocket server, you have several options: authenticate during the initial WebSocket handshake by including a token in the URL or a custom HTTP header, authenticate immediately after the connection using the first message from the client, leverage existing session IDs, or use tokens from OAuth or external providers. Use WebSocket Secure (WSS) with TLS/SSL to ensure the security of the authentication tokens and data transmitted. The choice of method depends on your application requirements and architecture, and you should also consider the management of token expiration and renewal due to the long-lived nature of WebSocket connections.

[@IsraelAlfaro]

@@apm thanks so much! Would you mind recommending another video/tutorial/post I could use as a reference, to follow along? Thanks once more!

[@apm]

@@IsraelAlfaro more information is on the Data-Driven Engineering course website, freely available at apmonitor.com/dde

[@UncleDavid]

can you make a tutoriel-if possible-on sending HTML over websocket without js

[@DuneKraftwerk]

Websocket is a library, you need a program to load this library, like js for instance and then sending a html strings will be possible

[@Anorch-oy9jk]

if my server also has to handle api calls, how can I combine that? I know how to asnyc it, but my issue is the server IP. Locally I use fast api and a ws endpoint. But once deployed with https protocol, the ws endpoint no longer works

[@apm]

You need to switch to wss instead of ws for https protocol.

[@Anorch-oy9jk]

@@apm managed to do it! The clients needed to do a handshake cause the server was secured hosted as https and so the ws endpoint also switched to secured wss.

[@GuruHomelander]

bro why u speaking in 0.25

[@apm]

Yes, I'm speaking slowly. Fortunately, CZcams allows you to increase speed up to 2x :)

[@upsenloyn]

​@@apmgood one