Port get_bsos' pagination optimization about syncstorage-rs HOT 4 CLOSED

Is this related to #205?

from syncstorage-rs.

Is this related to #205?

Nope, this is different.

It involves encoding some more information into the next_offset value passed to the client and an accompanying decoder of said value (as the client passes it back in to the service)

from syncstorage-rs.

Quick overview of work:

• Create new struct for Offset {timestamp: Option<SyncTimestamp>, offset: i64}
  • Include impl for From, Debug, etc.
• Convert Paginated to use offset: Option<Offset>
• Modify Mysql & Spanner to use new Offset heuristic
• Add tests

from syncstorage-rs.

A new struct may not be totally necessary if offset is just a String. The encode/decode methods can return the extracted types.

On the other hand the extractors could be responsible for producing this new struct and could even potentially validate the format.

This is an optional optimization, so the python version leaves impl. of it up to the db layer, for it to decide if it wants to support it

from syncstorage-rs.