Decide about blobs compatibility, requirements and specs
We have to collectivelly decide about backwards compatibility, requirements and specs for blobs implementation.
Backards compatibility
Some questions:
- Will we try to make blobs backwards compatible?
- What reasons do we have to want backwards compatibility?
- Does it make sense to have blobs-enabled server with blobs-unable client?
- Does it make sense to have blobs-unable server with blobs-enabled client?
- Are there other questions we need to answer to decide on this?
Some initial thoughts about the question "should the feature be backwards compatible"?
-
yes, you can turn it off and everything works:
- data would be stored in the same place it is stored now, both in client and server
- only transfer would be delayed.
- we would need to guarantee consistency in this behavior, which will probably end up in a complex solution
-
no, new place for data and no server to serve it.
- this is the route we were going so far.
- no possibility of getting data with old client/server.
- no consistency issues between sync lines (usual vs blobs), but also no fallback (if blobs fail, all data on it will be unavailable)
Requirements and specs
We already have a proposal for requirements. We have to review whether that is actually what we need, decide how to proceed with this.