Building a source: Roundtripping operations through firebase

[opsb]

In orbit-firebase operations are roundtripped asynchronously, but without promises i.e.

firebaseSource: transform(operation){
    firebase.saveChanges(operation);
}

to keep things consistent between all listening clients (not just the one that emitted the transformation) the response is then delivered via a websocket i.e.

firebaseListener.on("didTransform", function(operation){
    cache.transform(operation);
})

the firebaseListener registers listeners using the firebase client and then converts any received events back into operations which are applied to the cache. This means that there's no way to track the ancestry...

Possible approaches:

1. Ignore the ancestry issue - I've already seen sequencing issues that are most likely caused by a lack of this information.

2. Maintain operation queues on firebase - this means that the operations are stored verbatim in firebase and delivered in their original form to any listening clients. Getting this to work with firebase's approach to security is going to be difficult though...

@dgeb if you have any suggestions or input at all I'd be very happy to hear it :)

[opsb]

I'm now using a different approach to handle this so it's not relevant.