The write session, as the one holding the token tells it — read, never renewed.
The core does not know it: the token belongs to whoever authenticates the requests — the
connector when it manages the session itself, the host when it hands its own token over. So
the holder TELLS it, through GeoLeaf.Sync.registerSessionReader.
valid — a token is held, and its expiry is ahead.
expired — a token is held, and its expiry has passed. Whether it can still be renewed is
the server's call, when the network is back.
absent — no token: captures made off-network will wait for a sign-in.
The write session, as the one holding the token tells it — read, never renewed.
The core does not know it: the token belongs to whoever authenticates the requests — the connector when it manages the session itself, the host when it hands its own token over. So the holder TELLS it, through
GeoLeaf.Sync.registerSessionReader.valid— a token is held, and its expiry is ahead.expired— a token is held, and its expiry has passed. Whether it can still be renewed is the server's call, when the network is back.absent— no token: captures made off-network will wait for a sign-in.