Websockets

[daurnimator]

• framing functions
• client side
• server side
• documentation
• example
• tests

[RyanSquared]

22:49:40    <~daurnimator>  though I'm considering renaming send => write
22:49:47    <~AlissaSquared>    Yes, that's what I was about to ask about
22:49:57    <~AlissaSquared>    send/receive and read/write are typically what's used.

[daurnimator]

I just renamed :read to :receive. See the commit message for more rationale.

[coveralls]

Coverage increased (+0.004%) to 84.757% when pulling ad43394 on websockets into d59a831 on master.

[coveralls]

Coverage decreased (-4.6%) to 80.168% when pulling 6309bee on websockets into d59a831 on master.

[coveralls]

Coverage decreased (-2.5%) to 82.23% when pulling 61bf718 on websockets into d59a831 on master.

[coveralls]

Coverage decreased (-0.6%) to 84.143% when pulling 4f0515f on websockets into 101f0b7 on master.

[daurnimator]

API question: How should error codes be returned to the caller.
e.g. you call :receive; the peer causes a in-frame protocol error: you have multiple error codes to pick between:

1. the code you send to the peer informing them of their error
2. the code you receive in their acknowledgement of the error
3. a generated errno

2. is currently stored in ws.got_close_code, so I've tentatively picked option 1.

[coveralls]

Coverage increased (+0.02%) to 84.814% when pulling 81d21c4 on websockets into 101f0b7 on master.

[coveralls]

Coverage increased (+0.04%) to 84.833% when pulling f456f75 on websockets into 101f0b7 on master.