{"push_id":2021864615,"size":1,"distinct_size":1,"ref":"refs/heads/master","head":"337fcdfb4b45b556f4ce1b53f5235fa9e3c667ce","before":"f0816c78a38c623945ef881adddc5916bbc7b15c","commits":[{"sha":"337fcdfb4b45b556f4ce1b53f5235fa9e3c667ce","author":{"name":"Neil Jenkins","email":"d3e2a8ddc5fff5556efd7676e64f33f296044cb9@nmjenkins.com"},"message":"Improve Push conformance with RFC8030\n\n* Add optional support for encryption, resolves #110\n* Document that clients should use the ping event to help detect when buffering\n  proxies are interfering. Resolves #108.\n\nThe semantic changes can be summarised as:\n\nWeb Hooks\n* (get|set)PushCallback have been renamed (get|set)PushSubscription, aligning\n  with the terminology in RFC8030 and take a PushSubscription object as an\n  argument/response rather than just a URL.\n* The PushSubscription can have an expires time and encryption keys.\n* Push callbacks no longer have `X-JMAP-EventType`/`X-JMAP-User` headers, as\n  they are not needed.\n* Push callbacks MUST have a `TTL` header, and MAY have `Urgency` and/or\n  `Topic` headers, as specified in section 5 of [@!RFC8030].\n\nEventSource\n* Clients can now choose the ping time by adding a query parameter to the event\n  source URL.\n* Clients can now add a query parameter which causes the server to close the\n  HTTP response after pushing a state change (long-polling mode).","distinct":true,"url":"https://api.github.com/repos/jmapio/jmap/commits/337fcdfb4b45b556f4ce1b53f5235fa9e3c667ce"}]}
{"actor":{"display_login":"neilj"}}