Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
- I had issue with a hello world locally - bugs reported on Discord that happened on a server and not locally - bug reported on the Cookbook (issue 447) and un-answered issues https://github.com/fukamachi/websocket-driver/issues although that happens. It is a known and used lib so let's "deprecate" its mention in the Cookbook with this warning rather than removing the entry right now.
- Loading branch information
7c242db
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
But Hunchensocket also have bugs, it couldn't work well unless modify it's code manually, no one submit PR right now :(
See joaotavora/hunchensocket#13
Only Portal works well out of box :D
7c242db
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Ouch, really? :S So we can move Portal up at least. What else can we do here?
Do you have an opinion about https://github.com/3b/clws ? It is old-ish…
7c242db
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I've made a simple test and it seems that there's nothing unacceptable in clws. Old is not an obstacle, at least it is better than Hunchensocket right now I think...
But it has a limitation that it depends on
libfixposix
, which seems not available on Windows... See 3b/clws#16As a little benefit, clws can discriminate between text and binary message, both work fine.
In fact it seems that we do not have a powerful and full-featured websocket implementation right now... Although there are bugs in websocket-driver, it has some important features: it is implemented on HTTP server, so it can share port with HTTP server using server's request routing, and support TLS/SSL (
wss:
) easily. I haven't found an easy way to implement these using Portal (maybe also clws), as I'm just a noob 😢Actually, what makes me give up websocket-driver is more than it's issues. When I receive a file which slightly larger (test in 200K+ screenshots, macOS 10.15, sending javascript ArrayBuffer) using websocket-driver, it's binary data will be messed up, which I can't bear. There is no such problem in other websockets. Trapped in my poor knowledge, I don't know why... 😭😂
Finally I should express my thank to awesome-cl, it is helpful and joyful. Thank you!
7c242db
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks a lot for the feedback (and the kind words), I'll send a PR with more information about the websockets libraries.