Add proprietary subscription API hint to Overview graph, separate it from Subscription graphs

bitfireAT / webdav-push

WebDAV Push: Draft

48 stars 0 forks source link

Closed rfc2822 closed 11 months ago

rfc2822 commented 11 months ago

[ ] Separate Subscription graphs (I suggest one graph per subscription method) from Overview graph
[ ] Overview graph:
- [ ] Depict possible proprietary subscription APIs somewhere. In the case of Google Calendar, a client (or maybe even the Push Director?) can subscribe to Google Calendar API: Push notifications, which would then act as an Application Server, but with a proprietary protocol (it will send POST /push messages, but in their format).

rfc2822 commented 11 months ago

@sunkup Would you mind doing that? We can yet talk about the proprietary subscription API part.