greg-m

6 ms·

1. 31.▲
   by greg-m 5y ago

   Hey, PM for R2 here! We're fully integrated with Workers, so you can write a Worker that calls additional logic when a request is made to the bucket's url. We have notifications, where a change to the bucket invokes a worker with
2. 32.▲
   by greg-m 5y ago

   Hey, PM for R2 here. We're still deciding on how we want to handle caching. We integrate with Workers, so manually caching is always possible. The catch is we're currently building for strong consistency - if we added a cache in
3. 33.▲
   by greg-m 5y ago

   Hey, I'm the PM for R2. Yes to range requests. Current object limit is smaller than that, but we don't have a fundamental restriction there. Shoot me an email to gmckeon [at] cloudflare.
4. 34.▲
   by greg-m 6y ago

   Hey, I'm the PM at Cloudflare for WebSockets on Workers. Support is still in beta, so we're still working through the timeout details here. With the Workers Bundled plan ( https://developers.cloudflare.com/workers&
5. 35.▲
   by greg-m 6y ago

   Yes, updates are guaranteed to happen exactly once or not at all. If the connection drops, the Worker will receive an error and can re-establish its connection to the Durable Object. The update may or may not have been successfully persist
6. 36.▲
   by greg-m 6y ago

   Durable Objects are globally unique, so it's guaranteed that there's just one instance with a given id.
7. 37.▲
   by greg-m 6y ago

   Thanks for the interest! We're keeping access limited at first so we can get experience operating the system. We'll be expanding continually over the next few weeks.
8. 38.▲
   by greg-m 6y ago

   Hey, I'm Greg, the PM working on Durable Objects at Cloudflare. As part of the private beta, we're looking to get feedback on the best way to price Durable Object so they're accessible for all applications - small or large.