You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently there is no abstraction over Google Calendar API's registered webhooks (Notification channels).
We are relying on custom tokens sent on each webhook registration to identify which resources to update. Along with that we're storing sync_tokens for resources in their respective models.
Currently there is no way to cancel a webhook because we are not persisting its channel_id. Which means even if we delete a resource from our system, we'll keep getting callback requests for those resources.
A new model called 'NotificationChannel' can provide a simple interface for dealing with this. A NotificationChannel can belong to any resource that is being watched. This will also eliminate the need to store sync_tokens in respective models.
The text was updated successfully, but these errors were encountered:
Currently there is no abstraction over Google Calendar API's registered webhooks (Notification channels).
We are relying on custom tokens sent on each webhook registration to identify which resources to update. Along with that we're storing sync_tokens for resources in their respective models.
Currently there is no way to cancel a webhook because we are not persisting its channel_id. Which means even if we delete a resource from our system, we'll keep getting callback requests for those resources.
A new model called 'NotificationChannel' can provide a simple interface for dealing with this. A NotificationChannel can belong to any resource that is being watched. This will also eliminate the need to store sync_tokens in respective models.
The text was updated successfully, but these errors were encountered: