network sync request
Closed this issue · 3 comments
I think it's important we provide our sync libraries in a way that people who use our APIs to build apps are not (technically or conceptually) coupled with firebase. I can see us wanting to retrofit a firebase-like API on top of photon, for example, and have apps switch over to using our own servers without any code changes. I think it might be a good idea to make the sync library not explicitly be "firebase sync" but instead just be cast as "object sync" (analagous to a PUN photon view that syncs transforms) and incidentally use firebase for now (which we can mention in the documentation.) Thoughts?
+1
I don't think it's critical for launch, and in-fact I rather like that we
are leveraging the web for this for the time being. Eventually, yes, we
should have our own.
On Mon, Apr 13, 2015 at 9:20 AM, eric-romo notifications@github.com wrote:
+1
—
Reply to this email directly or view it on GitHub
#11 (comment)
.
It has to be firebasesync unless we want everyone using our firebase
account, which may not be possible.
On Mon, Apr 13, 2015 at 3:14 PM, Gavan Wilhite gavan@altvr.com wrote:
I don't think it's critical for launch, and in-fact I rather like that we
are leveraging the web for this for the time being. Eventually, yes, we
should have our own.On Mon, Apr 13, 2015 at 9:20 AM, eric-romo notifications@github.com
wrote:+1
—
Reply to this email directly or view it on GitHub
#11 (comment)
.