Kevin Whitley (@kevinrwhitley) on X
Would love feedback from anyone/everyone on the upcoming itty-durable interface:
https://x.com/kevinrwhitley/status/1800355908436083017
Kevin Whitley (@kevinrwhitley) on X
I'm finally pretty happy with the upcoming itty-durable
API/interface.
For those not following, this:
1. Brings auto-persist to @CloudflareDev Durable Objects
2. Allows you to easily swap in your own external storage
3. Works perfectly in @honojs, if that's your flavor :)
Twitter
5 Replies
I would just want the magic that is happening to be well documented so i can understand what's happening but otherwise seems like a much nicer interface.
Idea for a future iteration: abstract the hibernatable websockets so that they can also use an rpc like interface from the client
Absolutely will be documenting the full lifecycle of how it works. Luckily, while there's a bit of Proxy dark-arts (like with most itty libs) to make it work, the entire source is super tiny, so it's very easy to explain - including a line-by-line "what's happening".
This look slick, but what I really want is RPC all the way to the browser client for any data that supports the structured clone algorithm.
That would certainly be a trick, wouldn't it? 🙂
This can at least get that back to your Worker or whatever called the RPC method... baby steps!
BTW -
itty-durable@next is available for play-testing as of a few minutes ago! Rough API docs with examples included in README.
https://x.com/ittydev/status/1800952641620451621itty (@ittydev) on X
itty-durable@next is available for play-testing!
This adds automatic, swappable storage to @cloudflaredev RPC Durable Objects! 🔥
https://t.co/x74wzU9JAh
Rough docs are included in the README, minus the included middleware for @ittydev itty-router & @honojs (not required).
Twitter