Behavior of blockConcurrencyWhile when used outside of durable object constructor
The examples for usage always show this being used in the constructor of a durable object to prevent concurrent execution of requests while initialization is not yet done. Is this the only way this should be used?
In our project we're using blockConcurrencyWhile in one of many routes handled by the fetch method. What is the expected behaviour in this case? How should requests or alarms that have already kicked of before calling blockConcurrencyWhile for another request behave? Will they be stopped or could they be executing concurrently?
In our project we're using blockConcurrencyWhile in one of many routes handled by the fetch method. What is the expected behaviour in this case? How should requests or alarms that have already kicked of before calling blockConcurrencyWhile for another request behave? Will they be stopped or could they be executing concurrently?
