I have some follow up questions for the same, can I DM you?
I have some follow up questions for the same, can I DM you?
Game should not exist after 19:20



fetch() context and not at the root). But decided the fetch context (only the namespace_id needed + location within that context) might be more worth it than having to force the users to find their account_id , the namespace_id and the Bearer token . Would've preferred a lot more ofc if it was available at the root, but ALAS. Here is the Cloudflare KV-specific docs!KV is not ideal for applications where you need support for atomic operations or where values must be read and written in a single transaction.In that regard I agree authorization is a good candidate, however lots of developers likely get it confused with authentication and session management — KV might not be a good case for sessions due to it being eventually-consistent. Thoughts I'd bring this up since I have had people on the team ask similar questions.
I think we are okay with the eventual consistency of KV as long as it's under a minute or two. and you will definitely attain that with Workers KV.PutOptionsBuilder { this: Object { obj: JsValue(Object({})) }, put_function: Function { obj: Object { obj: JsValue(Function(put)) } }, name: JsValue("27c43d0052d59077f496"), value: JsValue("{"description":"test game, don't register","players":{},"guests":[],"comments":[]}"), expiration: Some(1729279200), expiration_ttl: None, metadata: None }Game