Skip to content

Commit 876e75a

Browse files
Merge pull request #295867 from Ankit-MSFT/docs-editor/notification-hubs-push-notific-1741280167
Update notification-hubs-push-notification-registration-management.md
2 parents b64170d + 8ccb67d commit 876e75a

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

articles/notification-hubs/notification-hubs-push-notification-registration-management.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -333,4 +333,4 @@ await hub.UpdateRegistrationAsync(r);
333333
await hub.DeleteRegistrationAsync(r);
334334
```
335335

336-
The backend must handle concurrency between registration updates. Service Bus offers optimistic concurrency control for registration management. At the HTTP level, this is implemented with the use of ETag on registration management operations. This feature is transparently used by Microsoft SDKs, which throw an exception if an update is rejected for concurrency reasons. The app backend is responsible for handling these exceptions and retrying the update if necessary.
336+
The backend must handle concurrency between registration updates. Notification Hubs offers optimistic concurrency control for registration management. At the HTTP level, this is implemented with the use of ETag on registration management operations. This feature is transparently used by Microsoft SDKs, which throw an exception if an update is rejected for concurrency reasons. The app backend is responsible for handling these exceptions and retrying the update if necessary.

0 commit comments

Comments
 (0)