4 ms·
I have a personal project based on this approach (JSON over Websockets): https://quixical.com/ https://quixical.com/ It appears to work well. Security was toug
by dynamite-ready 6y ago
I have a personal project based on this approach (JSON over Websockets): https://quixical.com/ https://quixical.com/
It appears to work well. Security was tough work though (at least I thought it was). And scaling up, no matter what tech you have access to, can be costly.
Also, determining how to handle disconnections is quite an interesting UI problem. Auto reconnect might be an option, but then you need to think about a retry policy. And it can be harder than you think... Mobile phones drop connections with surprising frequency, so it's worth thinking about very early on.
- mathgladiator 6y agoSecurity is exceptionally interesting, and it is why my language handles privacy as a first class citizen. The scaling up is a challenge due to the lack of common investments. It can be made absolutely cheap, and it is way cheaper than polling. People that dismiss websockets have a point that it throws away decades of wisdom, but the winnings and potential are there. The challenge is curating the right ideas and educating everyone... is hard.