{"push_id":1057958501,"size":2,"distinct_size":2,"ref":"refs/heads/master","head":"90b666b6ab798e89c90a387afdfb2e0fd668ef05","before":"750aa9fba184ae41abb4cf7778e61b2e3496c1a3","commits":[{"sha":"829139fb2defeedc2455cf9364133ca6d41cb9e2","author":{"email":"16a9a54ddf4259952e3c118c763138e83693d7fd@jwilm.com","name":"Joe Wilm"},"message":"Add support for PING frame\n\nThe protocol specifies a few things that could not be handled here due\nto current Solicit APIs.\n\n> If a PING frame is received with a stream identifier field value other\n> than 0x0, the recipient MUST respond with a connection error (Section\n> 5.4.1) of type PROTOCOL_ERROR.\n\nand\n\n> Receipt of a PING frame with a length field value other than 8 MUST be\n> treated as a connection error (Section 5.4.1) of type\n> FRAME_SIZE_ERROR.\n\nWhen receiving a PING frame without the ACK flag set, the connection\nreplies with a PING frame having the ACK flag set. When an ACK is\nreceived, nothing is done.\n\nIn addition to supporting the PING frame of the HTTP/2 protocol, a\nmethod is exposed on the Async client to support sending PINGs as\ndesired by the client. This part of the feature is a bit half-baked as\nthe client has no way of getting the PONG. It wasn't clear how this\nAPI should work. At the very least, it provides a method which will send\nPING frames and return an error immediately if the client isn't capable\nof making requests.","distinct":true,"url":"https://api.github.com/repos/mlalic/solicit/commits/829139fb2defeedc2455cf9364133ca6d41cb9e2"},{"sha":"90b666b6ab798e89c90a387afdfb2e0fd668ef05","author":{"email":"677198fd502208ab9e390a8699b3ab45dd325d63@gmail.com","name":"Marko Lalic"},"message":"Merge pull request #21 from jwilm/add-ping-frame\n\nAdd support for PING frame","distinct":true,"url":"https://api.github.com/repos/mlalic/solicit/commits/90b666b6ab798e89c90a387afdfb2e0fd668ef05"}]}