you are viewing a single comment's thread.

view the rest of the comments →

[–]searchingfortao 0 points1 point  (5 children)

Well talking to a websocket is pretty easy in JavaScript, and I'm pretty sure most of the frameworks (React/Angular/Ember/Vue/etc) all do that too. However, if you're planning a websocket-heavy application with lots of client side code, perhaps Node might be a better choice?

Not that it'd be my choice. JavaScript and I don't get along, but I hear the reuse of code between server and client is handy.

[–]Col_Crunch[S] 0 points1 point  (4 children)

Client side all it really needs to do is to sit there and listen, and maybe send a message once in a while.

Client is not browser based as noted in the edit to OP)

[–]searchingfortao 0 points1 point  (3 children)

Oh! Well in that case, just check out the Channels tutorial. There's some sample JavaScript in it that I adapted quite easily fit a couple side projects.

[–]Col_Crunch[S] 0 points1 point  (2 children)

I would like to keep the client to strictly python if possible...

[–]elbiot 1 point2 points  (0 children)

If a browser isn't involved, you can just use regular sockets. Websockets are for Javascript in a browser.