actually it was stuck in the DB, but was removed from the codebase.
updated protobuf -> 420 validation errors.
Starting with the api side.
Starting session, here’s the token to save Expect the request to have a user token and device id. Furtive makes these. It also gives us a merchant, and we associate the rut with the mid.
because get user token is followed very closely by a get-buckets call, and we need to have the rut+did in the db before get-buckets asks.
most performance critical API call. Must be below 10ms as per SLA FOR SURE.
after we return a value for get-buckets we can look up.. something
update confirmed = true in session_buckets where rut = $rut, and bucket = $bucket.
s -> f: get-buckets (user token) f -> e: get-buckets (user token) e -> e: use hash to find buckets and inject buckets into [user token] e -> f: return new user token + buckets f -> s: buckets e -> db: update user token
staples -> Furtive: get-user-token () Furtive ->+ Eccentrica: get-user-token ()
Eccentrica -> db: use hash to find rut -> use hash to append bucket info to rut. Eccentrica –>- Furtive: return user token Furtive -> staples: return user token