On Fri, Apr 22, 2022 at 05:10:24PM +0200, Paul Gevers wrote: > I assume it's quite different from the nearly identical named > python-websockets, which we already have. Yes, it is. They serve a similar purpuse, of course: using WebSockets in Python programs. But the interface is very different. I'm not familiar with python-websockets, so I can talk about what python-websocketd does that it doesn't seem to do. Python-websocketd attempts to provide RPC functionality, making it work like the remote object is local. So you need to provide an object to the constructor (if you want calls to be made by the remote end). Then the remote end can call member functions of that object and receive the returned value. It can do so while blocking, or asynchronously. For security (by avoiding accidentally exposing functionality), data properties and member functions starting with an underscore cannot be accessed remotely. Thanks, Bas
Attachment:
signature.asc
Description: PGP signature