https://discord.cloudflare.com logo
Join Discord
Powered by
# durable-objects
  • h
    Wut
  • h
    Maybe that’s a Pages thing…
  • s
    that's in local mode, it's a bit different
  • h
    Oh, that makes sense
  • a
    will a 
    setInterval
    keep a DO alive?
  • k
    No. If there are no clients connected, the DO will shut down after a bit even if there's a future setInterval or setTimeout pending.
  • k
    To schedule tasks to happen reliably at some future point, use alarms
  • a
    got it! and what about pending network or async requests? do those keep the DO alive, or is it truly ONLY connected HTTP/WS connections?
  • u
    Afaik only active traffic to the object will keep it alive.
  • c
    Can anyone send me more advanced examples of durable objects?
  • h
    #992060581832032316?
  • h
    LogTail?
  • c
    For durable objects
  • h
    Both of those are built on #773219443911819284…
  • h
    Also, part of R2
  • c
    I'm already using R2, D1, KV..., but for this specific example DOs would be better option.
  • c
  • h
    I meant, you were asking for examples of what you can build on DOs? Those are some examples that are using DOs
  • c
    ohh, I mean like how to use them in a little more advanced example like manipulating with data, storing arrays, json, sending data to durable objects....
  • c
    the only example in docs is just increasing and decreasing the integer
  • c
    So you can supply data to DO thru json right?
  • s
    You interact through DOs from workers with requests, you can put whatever you want in the bodies of those requests
  • c
    Thanks
  • c
    So state.storage is like KV?
  • c
    key value store
  • s
    It's similar, yes
  • s
    But it's tied to each individual durable object, rather than data being shared across the whole namespace
  • c
    and if you put integer in state.storage it gets returned as string?
  • h
    No
  • h
    DO Storage can store anything that the V8 serializer can parse
1...526527528...567Latest