Hi, I have a usecase where I run websocket connections on a durable object. Some of the messages I r
Hi, I have a usecase where I run websocket connections on a durable object. Some of the messages I receive require making external API calls. These external calls are fairly slow (1-2 sec).
I don't want to block the durable object for that duration, so I thought that the durable object could invoke the worker (which also deploys the DO) without awaiting for the response, and then the worker would call back to the DO once the work is completed. But I can't figure how to make a binding that would allow the DO to call the same worker that deployed it.
I could make the call with the full DNS name that points to the worker, but then I will need to go through our CF access protection and that feels like a pointless complication.
So in short, is there a way to make a binding to "self" so that the durable object could call (rpc or fetch) the worker that deployed the DO.
I don't want to block the durable object for that duration, so I thought that the durable object could invoke the worker (which also deploys the DO) without awaiting for the response, and then the worker would call back to the DO once the work is completed. But I can't figure how to make a binding that would allow the DO to call the same worker that deployed it.
I could make the call with the full DNS name that points to the worker, but then I will need to go through our CF access protection and that feels like a pointless complication.
So in short, is there a way to make a binding to "self" so that the durable object could call (rpc or fetch) the worker that deployed the DO.
