21–30 of 37 posts
Looks really awesome!
Thanks! If you end up using telepat and have any questions / feedback, feel free to ping us @ founders@telepat.io
Which strategy do you use to sync data? (e.g. in the context of collaborative editing)
Earlier quoted context omitted.
Thanks! If you end up using telepat and have any questions / feedback, feel free to ping us @ founders@telepat.io
Great work on the architecture documentation. I'm looking at your repos on Github and I'm curious about something. What are you using to test telepat-api, workers, and the integration with all the third party projects listed in the docs?
Which strategy do you use to sync data? (e.g. in the context of collaborative editing)
Collaborating on different properties of a single object is no problem; for working on the same property we don't do diff/merge yet, it's just FIFO.
How do they make money?
1) Professional/Consulting services and support for paid users 2) Hosted version (SAAS) 3) Book deal 4) Paid client/server plugins for additional functionality 5) Get "aqui-hired" 6) Enterprise version that's more stable and battle tested 7) etc...
We'll share updates along the road, meanwhile - we're eager to talk to developers that are tackling real-time and refine the product together.
Hi, for node-only usage, how is this different from Racer[0] (part of DerbyJS)? [0]: https://github.com/derbyjs/racer
I don't like the fact that the Tux logo is linked to http://linux.com Should be http://kernel.org as linux.com has a spammy feeling..
Earlier quoted context omitted.
Collaborating on different properties of a single object is no problem; for working on the same property we don't do diff/merge yet, it's just FIFO.
So if two users are working on the same textfield there is no way to merge their changes at the moment?