2 ms·
Thanks for your feedback. I've just been playing with this stuff and wanted to put it out there despite its warts. Regarding the scaling issue. Yes. This is de
by HenrikJoreteg 16y ago
Thanks for your feedback. I've just been playing with this stuff and wanted to put it out there despite its warts.
Regarding the scaling issue. Yes. This is definitely a weakness (I actually mention it as a weakness in the last paragraph or so). We're working on a solution for that using redis as a sort of shared memory. But it's just not ready for primetime and I just figured I'd write up what I had going so far.
Regarding recursive updates of nested collections, the "mport" function in the post works well for re-inflating the entire state. But not quite as well for updates, but for this type of thing, I prefer piecemeal updates anyway, so we don't have to send as much data each time.
I'm definitely gonna check out dnode some more as well. Cheers.
- moe 16y agoI've just been playing with this stuff and wanted to put it out there despite its warts. And thanks for that! In hindsight my first reply came out more nitpicky than intended; all my concerns are aimed at (still to be fixed) shortcomings in the backbone/node ecosystem, not at your particular implementation. Major kudos for not only coming up with (at the very least) an intriguing Proof Of Concept but then also writing a great blog post to describe it. This will be learning material for myself and many others.
- HenrikJoreteg 16y agoThank you. No offense taken :)