Calling PushManager.subscribe() should always hit the GCM Driver
The PushMessagingManager currently maintains its own subscription cache in the Service Worker database, keeping track of the subscriptions it thinks are valid. This means that the PushMessagingManager assumes that the subscription is valid. There are cases where the underlying push service, in our case Google Cloud Messaging implemented through our GCM Driver, invalidates a subscription. We need to find out about that when it happens, so change the PushMessagingManager to *always* attempt to create a subscription, upon which we rely on the push service client to return the same information given the same input. The GCM Driver has its own cache, so in the vast majority of cases these calls won't hit the server. They will, however, on occasion. Bug: 799483 Change-Id: I715c6f2eb8296b4512b6b7e9e31734ce9f254744 Reviewed-on: https://chromium-review.googlesource.com/932401 Commit-Queue: Peter Beverloo <peter@chromium.org> Reviewed-by:Anita Woodruff <awdf@chromium.org> Reviewed-by:
Tom Sepez <tsepez@chromium.org> Reviewed-by:
Avi Drissman <avi@chromium.org> Cr-Commit-Position: refs/heads/master@{#539473}
Showing
This diff is collapsed.
Please register or sign in to comment