On some 32-bit architectures, 64-bit atomic operations panic when the
value is not aligned properly.

In this package, this causes netConn operations to panic when compiling
with GOARCH=386, since netConn does atomic operations with int64 values
in the netConn struct (namely, with readExpired and writeExpired).

This commit fixes this by moving readExpired and writeExpired to the
beginning of the struct, which makes them properly aligned.

Not sure how/when this was lost but an important disadvantage to note.

Whoops, updates #254 and closes #410

Whoops.

v1.8.8

Tricky tricky.

Underscores in symbols are ok sometimes...

No longer needed :)

Closes #330

Closes #330

Closes #330

Updates #330

Glad no one ran into this in production.

Closes #405

You should always be reading from the connection with CloseRead so this shouldn't
have affected anyone using the library correctly.

Closes #355

Closes #298
Closes #394

The close frame was being received from the peer before we were able to reset our
write timeout and so we thought the write kept failing but it never was...

Thanks @univerio and @bhallionOhbibi

Updates #298

Closes #400

Reject invalid "Sec-WebSocket-Key" headers from clients