3
78%
master: 78%

Ran 05 Apr 2016 04:55PM UTC

Files 21

Run time 5min

Badge

Embed ▾

Committed 04 Apr 2016 09:24PM UTC coverage: 93.663% (-1.3%) from 94.919%

Job # 421.3

Build Type

Pull #21

travis-ci

Committed by

jwilm

Commit Message

Add support for PING frame

The protocol specifies a few things that could not be handled here due
to current Solicit APIs.

> If a PING frame is received with a stream identifier field value other
> than 0x0, the recipient MUST respond with a connection error (Section
> 5.4.1) of type PROTOCOL_ERROR.

and

> Receipt of a PING frame with a length field value other than 8 MUST be
> treated as a connection error (Section 5.4.1) of type
> FRAME_SIZE_ERROR.

When receiving a PING frame without the ACK flag set, the connection
replies with a PING frame having the ACK flag set. When an ACK is
received, nothing is done.

In addition to supporting the PING frame of the HTTP/2 protocol, a
method is exposed on the Async client to support sending PINGs as
desired by the client. This part of the feature is a bit half-baked as
the client has no way of getting the PONG. It wasn't clear how this
API should work. At the very least, it provides a method which will send
PING frames and return an error immediately if the client isn't capable
of making requests.

Pull Request Pull Request #21: Add support for PING frame

Coverage Stats

2882 of 3077 relevant lines covered (93.66%)

0.94 hits per line

mlalic / solicit / 421 / 3
78%
master: 78%

README BADGES
x

Markdown

Textile

RDoc

HTML

Rst

Source Files on job 421.3

mlalic / solicit / 421 / 3 78% master: 78%

README BADGES x

Markdown

Textile

RDoc

HTML

Rst

Source Files on job 421.3

mlalic / solicit / 421 / 3
78%
master: 78%

README BADGES
x