3 ms·
WebSockets are really cool but we found the browser implementations unstable enough that we switched back to XHR for Tinkercad. Especially since the secure impl
by kaib 16y ago
WebSockets are really cool but we found the browser implementations unstable enough that we switched back to XHR for Tinkercad. Especially since the secure implementations were super shaky and we run all our traffic over SSL.
We also use Go and not Node.js for the backend so the only thing qualifying us for this perfect storm is WebGL.. :-)
- deleted 16y ago[deleted]
- pauldix 16y agoTotally agree with this. We were using WebSockets initially and it worked great in Chrome and not too well everywhere else. We got the exact same user experience/effect by switching over to XHR with a fairly frequent polling interval. It's much more reliable and we found it easier to program, test, and debug.
- MatthewPhillips 16y agoI'd love to see a blog about your experience with using Go as your web server. Did you use the standard library, Web.go, or something else? There have only been a few deploy production web apps with Go so far, so the knowledge needs to spread.
- kaib 16y agoFor Tinkercad the http server is just a relatively simple transport layer, the magic happens with how the computation is distributed in the cluster. We'll blog about it once things settle down a bit, at this point we are just trying to soldier ahead with the beta. :-)