Basic requirements

[rfc2822]

• Change element hierarchy and names to current draft

  • There's now a normative formal reference (although it may still change): XML Schema.

• Handle subscription registration

  • handle requested and cap to a reasonable default (1 week) – Handle expiration #23
  • returns Expires header – reasonable default (1 week) – Handle expiration #23
  • returns Location header

• Handle subscription update

  • returns Expires and Location, like on registration

• Handle subscription removal – DELETE on a subscription doesn't delete from oc_dav_push_subscriptions_webpush #17

• Notification:

  • on add calendar object
  • on change calendar object
  • on delete calendar object – Deleting an event or task does not push #30
  • contains collection sync-token
  • contains collection topic

• Clean up expired subscriptions – Handle expiration #23

• Clean up invalid subscriptions – Handle invalid subscriptions #24

  • at least the one that return 4xx, others may be kept until they expire

[rfc2822]

Wow, cool! So I'm closing this issue and create new ones when anything pops up.

[bonswouar]

Does this mean that

push subscriptions currently don't expire and won't be removed when they have become invalid

can be removed from the README? :)