3
100%
master: 100%

Ran 12 Mar 2016 03:58PM UTC

Files 2

Run time 0s

Badge

Embed ▾

Committed 12 Mar 2016 02:44PM UTC coverage: 96.429% (+0.2%) from 96.277%

Job # 159.3

Build Type

push

travis-ci

Committed by

bigeasy

Commit Message

Create a single end point for messaging.

This makes it simpler to implement in an existing server, or to wrap a
server around it quickly, only one end point and you hand the messages
off to the Kibitzer. It would be simpler to implement, but not very
restful. This isn't an API however, no one else is supposed to use these
end points.

This seems like you have an intuition and the only thing holding you
back is pedantry. There's something about designing an API for this that
invites unwanted consideration from the user. In this case, HTTP is just
a transport that makes some guarantees. It is below the application in
the network stack.

Run Details

189 of 196 relevant lines covered (96.43%)

4.4 hits per line

Source Files on job 159.3

Coverage	∆	File	Lines	Relevant	Covered	Missed	Hits/Line

bigeasy / kibitz / 159 / 3
100%
master: 100%

README BADGES
x

Markdown

Textile

RDoc

HTML

Rst

Source Files on job 159.3

bigeasy / kibitz / 159 / 3 100% master: 100%

README BADGES x

Markdown

Textile

RDoc

HTML

Rst

Source Files on job 159.3

bigeasy / kibitz / 159 / 3
100%
master: 100%

README BADGES
x