Closed Gaelik-git closed 1 month ago
I agree timeout
is not a perfect name but lock_expiry
is just incorrect. I tried to find the same implementation in other SDK (go, js or java) but they I think they all use the amqp
api not the http api so it's difficult to compare
Edit:
In the python SDK we have this description for the timeout
timeout: Optional. Timeout for the http request, in seconds
lock_expiry is not correctly named, and give incorrect indication about the behaviour. I could not found documentation about this on azure but my experiences show that it represents the time after which the http connection send 204 empty response if no message is available
When using a timeout of 100s I get the following debug log from hyper (reqwest)
On this api doc 204 response is described as
No messages available within the specified timeout period.