Expose JSONDecodingError from proto module.
fix handler reference, self.handler would be None in this case
Merge pull request #9 from Simperium/handlerfix

fix handler reference, self.handler would be None in this case
Merge branch 'master' of https://github.com/mrjoes/sockjs-tornado
Optional IP validation.
Use SockJS 0.2 by default.
SockJS 0.3 support.
Bumped version and added changelog.
Fixed support for older simplejson library versions.
Fixed installation script, bumped version.
Fixed typo.
Pedantic fix, 1st arg to classmethod is cls
Merge pull request #14 from davbo/master

Pedantry - first arg to classmethod is cls not self
Minor formatting changes in README.rst
Merge pull request #15 from reclosedev/patch-1

Minor formatting changes in README.rst
Fixed #20, added whitelist of exposed headers

exposes useful headers in the connection info object: 'referer', 'x-client-ip',
'x-forwarded-for', 'x-cluster-client-ip', 'via', 'x-real-ip'
Merge pull request #21 from melevine/headers

Fixed #20, added whitelist of exposed headers
Added the request path to the ConnectionInfo class
Merge pull request #22 from melevine/requestpath

Added the request path to the ConnectionInfo class
Allow the binary option to be bubbled down from send to rawwebsocket's
write_message.

It's not currently possible to send a message over the sockjs-tornado
"rawwebsocket" as binary instead of utf8.

Websocket defines both TextFrame and BinaryFrame when sending messages,
and there are different opcodes for each. This leads to issues with for
example when iOS websocket clients receives a TextFrame with binary in it.

Only the rawwebsocket's tranport has been updated to alter behavior when
the binary flag is set, as the other transports are javascript specific,
and javascript doesn't have support for binary.