Help me understand why we need a second flag day when changing wire formats or storage formats.
Andreas Sent from Mobile. On Aug 9, 2013, at 18:02, Brian Warner <war...@mozilla.com> wrote: > On 8/9/13 4:37 PM, Lloyd Hilaiel wrote: > >> So I'd like to open a venting thread here. Let's capture once and for >> all the real, actual, user facing or implementation complexity >> downsides of implementing a new authentication flow and grafting it >> onto Sync 1.1. > > I expect rnewman will express this better than I can, but he mentioned > this morning that we basically get one flag day. It's not the super-bad > "everybody must change at the exactly same time" kind of flag day. But > it's a still-kinda-bad "everybody must do a one-way account upgrade > during some multi-month overlap between new-servers-launched and > old-servers-shut-down window" upgrade/flag-day. > > If we use that upgrade to get from Sync1.1+OldAuth to Sync1.1+NewAuth, > we'll land on a system that is known to be fragile, and about which I've > heard scalability/ops problems. To upgrade from there to a more > stable/scalable protocol, we'd need a second flag day, and that'd be too > embarrasing to pull off. > > cheers, > -Brian > _______________________________________________ > Sync-dev mailing list > Sync-dev@mozilla.org > https://mail.mozilla.org/listinfo/sync-dev _______________________________________________ Sync-dev mailing list Sync-dev@mozilla.org https://mail.mozilla.org/listinfo/sync-dev
