On 12/08/2013 10:50 PM, Lloyd Hilaiel wrote:
> On Aug 12, 2013, at 4:26 AM, Ryan Kelly <[email protected]> wrote:
>> More generally: if this really is the only other
>> absolutely-must-have-before-flag-day feature, then let's get it nailed
>> down ASAP.
>>
>> Thoughts?
>
> I'm four on the positive side for an approach like this. The only missing
> bit would seem to be the server knowing what "version" of storage you're on.
> A connected client can say "oh look, all versions of a users device support
> fancy-new storage back end, and I'm back on crufty sync X.Y, let me migrate".
>
> Then other devices come on line and say "oh look! I've got a local crufty
> version of data, but the database was updated, let me ditch this old
> code-path and re-sync with the new hotness".
Right. This starts to feed into an as-yet-undefined "service discovery"
component. One of the devices would look around, figure out "oh it's
time to update" and then tweak some sort of service-discovery document
to say "ok folks, now we're using storage format X over on server Y".
If we can spec out and ship that before flag-day as well, so much the
better. But technically, push-comes-to-shove, we don't need to ship
that yet - we could get away with "devices below version X don't support
service discovery" and upgrade to this richer model at a later date.
> On 13/08/2013 5:04 AM, Chris Karlof wrote:
> I need to think more about the tradeoffs of where to put device management.
> There are compelling reasons for the FA server to manage them. When I think
> about getting the "last synced" time for each device, it seems more natural
> for this information to be stored on the storage server. Maybe that just
> means two API calls to show a list of devices with the times they last synced.
Completely agree, this kind of service-specific metadata does not belong
in the account server. Doing a separate request to discover it from the
storage server seems OK to me.
Tangent: we could in fact build out a separate "device coordination
service" that stores more detailed device meta-data, allows devices to
send push-notifications to each other, subsumes Sync1.1's "client
command" functionality, etc. That's not MVP, but may be a useful
direction for the future.
Cheers,
Ryan
_______________________________________________
Sync-dev mailing list
[email protected]
https://mail.mozilla.org/listinfo/sync-dev
