azure-service-bus-dotnet
azure-service-bus-dotnet copied to clipboard
Azure
Allow message scheduled enqueue time to be expressed with TimeSpan
Message.ScheduledEnqueueTimeUtc accepts DateTime. There's a problem with this approach - calculated time is based of the local clock and not the broker lock. The client cannot know the server time either. Allow deferring message enqueue operation by providing delay as TimeSpan (similar to lock duration). With this approach the server will be using its own clock, w/o the need to worry for the client to be in sync.
@jtaubensee not sure if the broker support this or not, so could be more than just a client side.
@SeanFeldman , do you expect the variance in machine clocks (for UTC) be considerably more than the variable in the latency of the send scheduled message request?
Closing this issue as it is already opened the service side repo: Azure/azure-service-bus#40
@nemakam the server side is to allow this call. Should this stay in place to be added to the client?
Makes sense. I'll reopen the case. Will close it if required after the initial triage on the other repo.