id still try it, there is 1 get, and who knows if the get is doing something funny w schema reads
id still try it, there is 1 get, and who knows if the get is doing something funny w schema reads
<mobile-phone>-<OTP> and value being the timestamp or whatever info you want. When the request comes in you can check the specific OTP if it exists or not indicating validity, and search by prefix the phone number.npm create cloudflare@latest hello world template with DO, change to SQLite backend, with the following code: https://gist.github.com/NonSpicyBurrito/f4938faa7a779574d9af945d012f6703. Deploy, send two requests far enough apart so they can show up separately on dashboard, and observe DO metrics:rowsRead/rowsWritten it's what I would expect. I will share it with the DO team to see if they find anything.During the initial beta, Storage API billing is not enabled for Durable Object classes using SQLite storage backend. SQLite-backed Durable Objects will incur charges for requests and duration. We plan to enable Storage API billing for Durable Objects using SQLite storage backend in the first half of 2025 after advance notice with the below pricing.
wss:// used to work just fine. We only used 1 Durable Object Rpc to do a 50s form filing process using the remote browser. This worked great.puppeteer.connect:Requests that hit the Durable Objects in-memory cache or that use the multi-key versions of get()/put()/delete() methods are billed the same as if they were a normal, individual request for each key.https://developers.cloudflare.com/durable-objects/platform/pricing/#key-value-storage-backend
this.ctx it's part of the DurableObject class
