Teoman Soygul

I didn't setup auto builds since Docker Hub requires full access to my private repos but it might change in the future. https://docs.docker.com/docker-hub/builds/

As per Go testing docs (http://golang.org/pkg/testing/#hdr-Examples), test functions are compiled but not executed if they do not have concluding line that begins with `Output: ....` statement. We should add that...

Separate CCS communication logic from queueing logic (which should be common for both HTTP & CCS)

1

dequeue tip: "message_type":"receipt" as described here: https://developer.android.com/google/gcm/ccs.html#receipts

When we get following in response to a message with broken stanza (as described here: https://developer.android.com/google/gcm/ccs.html#stanza): ``` xml {"random": "text"} InvalidJson: JSON_PARSING_ERROR : Missing Required Field: message_id\n ``` The resulting...

We can use sequential numbers optionally, just as the Android client does (1, 2, 3..) in upstream messages. Cluster ID (process ID) can be prefix like: a1, b1, a2...

Use error types specific to a given error along with extra info fields (maybe not? and simply favor simplicity). Either way, return type should always be `error` in method signature...

or just `return errors.New("connection closed")` not handling them at all is also an option (as in `tls.Conn` function which never account for closed connection)

Classical security vs stability tradeoff. Being a web service API, security wins so it's time to let the patch versions float.