Speaking at a very high level: so long as you version the protocol, version
the data format, and strongly define the types in the format (none of the
"sometimes a number, sometimes a number as a string" crap we have in Sync),
I'm happy.
Remember that users don't upgrade clients as often as we'd
*Today's Theme: Items in danger & may not make train*
https://public.etherpad-mozilla.org/p/fxa-engineering-coordination
Shane
___
Dev-fxacct mailing list
Dev-fxacct@mozilla.org
https://mail.mozilla.org/listinfo/dev-fxacct
On 28/04/2016 6:03 PM, Rémy Hubscher wrote:
Hi all,
For the AMO blocklist project, we are working on in the storage team, we
are using JSON Schema validation to make sure clients and servers are on
the same page (the administration panel, the gecko client and the
importation/exportation scripts
Hi all,
For the AMO blocklist project, we are working on in the storage team, we
are using JSON Schema validation to make sure clients and servers are on
the same page (the administration panel, the gecko client and the
importation/exportation scripts as well as the storage layer.)
IMHO, It is
My $0.02: I'm pro-validation but ambivalent about JSON Schema specifically.
However it should be straightforward for the auth server to convert from
JSON Schema to Joi validation objects via, e.g.
https://www.npmjs.com/package/enjoi, provided we can stick to the subset
that is implemented there
Hi all,
Edouard has been working on adding payloads to our push messages and
we were having a bit of a discussion about how to define these payloads.
This is becoming relevant to FxA and to Sync, hence I'm copying both lists.
When defining the data in a payload for a certain message, both
6 matches
Mail list logo
