News for hackers. Stuff that matters.

gabidobocan

Thanks!

Yes you can (and should) also intercept at kernel level, but the kernel can't tell which of your app's dependencies is responsible for the call, only the application knows that.

Re:Firebase expands to become a unified app platform on Wednesday May 18, 2016 @05:53PM (#11726299)
We were also looking for an open source Firebase a while ago, packed with some extra features like multiple db support and push notifications. Ended up building http://telepat.io.

Docs & specifications at http://docs.telepat.io/. Hope this helps you.

Re:Telepat: Real-Time, Open Source Data Sync on Wednesday September 02, 2015 @05:54PM (#10162149)
Racer is great at synchronizing objects, and more flexible than Derby. One key difference between Racer and Telepat is that the Racer client needs to run within a JS container, while Telepat offloads native functionality to native clients. I'd say we're more mobile and user-access oriented than Racer, basically, but we're more architecturally apart as well.
Re:Telepat: Real-Time, Open Source Data Sync on Wednesday September 02, 2015 @10:15AM (#10159276)
Not yet - unless you do it client-side. We're working on having a proper implementation for this use case.
Re:Telepat: Real-Time, Open Source Data Sync on Wednesday September 02, 2015 @09:36AM (#10159017)
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.
Re:Telepat: Real-Time, Open Source Data Sync on Wednesday September 02, 2015 @08:27AM (#10158697)
Thanks! Offline support is on the roadmap - the iOS and Android clients actually already use a local database, so we're nearly there.
Re:Telepat: Real-Time, Open Source Data Sync on Wednesday September 02, 2015 @07:52AM (#10158577)
Good question, we get this asked a lot (usually in relation with companies such as PubNub or Pusher.io). It's different in a number of ways: - it's compatible with any number of protocols (we call them transports). Currently, we support websockets, APNS and GCM. MQTT could easily be added as a transport protocol for subscribing to channels - it also handles data aggregation (for example if you have a large number of updates on an object in a short amount of time, the system will aggregate them and send only the relevant updates to the subscriber) - it's more open (in my opinion) as it's designed to enable developers to swap out one component for another (and writing a thin adapter for it if it's not already available). This should also mean that the whole system can be better optimized depending on the workload type and use-case.
Re:Telepat: Real-Time, Open Source Data Sync on Wednesday September 02, 2015 @07:39AM (#10158534)
Hey everyone, one of the founders here! We've written a blog post that pretty much sums up our vision on real time infrastructures and our drive for this product. Have a look: http://blog.telepat.io