Show HN: Nodal. Next-Generation Node.js Server and Framework

Re:Show HN: Nodal. Next-Generation Node.js Server and Framework by bryanlarsen on Wednesday January 06, 2016 @08:13AM (#10850288)

Another reason : you can send ops over the wire rather than data. For example, you can send "add 7 to x" when the user makes a change rather than "set x to 21". Then you use the same code on server and client side to execute the ops.

If you structure your ops to be reorderable and composable you can get nice stuff like multi user editing, arbitrary undo, multi data centre synchronization, etc.

See the google docs papers for more details.

[ Parent | on HN ]

Re:Show HN: Nodal. Next-Generation Node.js Server and Framework by paulpepper on Wednesday January 06, 2016 @08:47AM (#10850430)

Can you offer any references to the google docs papers that you refer to?

[ Parent | on HN ]

Re:Show HN: Nodal. Next-Generation Node.js Server and Framework by bryanlarsen on Wednesday January 06, 2016 @08:57AM (#10850468)

Google for "Operational Transformation". That turns up lots of good stuff. The wikipedia article includes links to Google Wave papers, which I think is the papers I'm referring to. It's been several years since I read them, though.

[ Parent | on HN ]