159
100%

Ran 12 Mar 2016 03:58PM UTC

Jobs 3

Files 2

Run time 7s

Badge

Embed ▾

pending completion

Build # 159

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.

Coverage Stats

189 of 196 relevant lines covered (96.43%)

13.19 hits per line

Jobs

ID	Job ID	Ran	Coverage
2	159.2	12 Mar 2016 03:58PM UTC	96.43	Travis Job 159.2
3	159.3	12 Mar 2016 03:58PM UTC	96.43	Travis Job 159.3
4	159.4	12 Mar 2016 03:58PM UTC	96.43	Travis Job 159.4

Source Files on build 159

Detailed source file information is not available for this build.

bigeasy / kibitz / 159
100%

README BADGES
x

Markdown

Textile

RDoc

HTML

Rst

Jobs

Source Files on build 159

bigeasy / kibitz / 159 100%

README BADGES x

Markdown

Textile

RDoc

HTML

Rst

Jobs

Source Files on build 159

bigeasy / kibitz / 159
100%

README BADGES
x