1254402 - Use info/configuration endpoint to decide on maximum upload sizes

Status: NEW

(Firefox for iOS :: Sync, defect, P3)

Description

[Richard Newman [:rnewman]]

See Bug 1250747, Bug 1250189.

We should do the same on Android and desktop, too.

Comment 1

[Stephan Leroux [:sleroux]]

Looking through the discussion https://bugzilla.mozilla.org/show_bug.cgi?id=1250189, would it make sense to implement this prior to implementing atmoic uploads/batching so we can upload batches more intelligently?

Comment 2

[Richard Newman [:rnewman]]

There's no way to use a custom server config on iOS, and these numbers aren't likely to change much, so if we're careful about not shipping batch uploads until the batch API is supported in prod, we can hard-code numbers.

The _right_ thing to do is to use this API, and it shouldn't be hard to do… but it doesn't block.

Comment 3

[Richard Newman [:rnewman]]

This is now actionable -- the server code is deployed -- so we should do this. Clearing triage flags for re-triage.

This allows the client and server to negotiate how many records we put in each HTTP POST (typically more than the default of 100).

This means we can do dramatically better wrt power and network usage, allow syncs to complete more quickly, and also let us adapt to network types if we so choose.