Release 0.1.1.5

 * Catch unicode errors
Make handshake less strict with ts and payload

According to the RTMP specification, client's ACK message (C2) must include
the timestamp and payload from server's SYN message (C1). After some
observations done with a Wowza publisher against an Adobe Media Server,
we concluded that those requirements are completely ignored by both
sides and, even worse, Wowza publisher sends completelly bogus data and
timestamps in all the messages involved with the handshake breaking any
attempt to follow the specification.

Having this in mind, we decided to remove the hard check in the
ServerNegotiator to allow publishers like Wowza to still work even if
they fuck with the handshake.
Implement onStatus and onHeaderData methods

Those methods are called in the server when using a wowza publisher. We've
left them unimplemented for now because there is no need to handle the
data they provide right now. This will just prevent ugly tracebacks in
the logs.
Don't require client's BW negotiation to connect

In some cases, the client may not send the bandwidth negotiation
packets to the server. If this is the case, the server can be stuck
waiting for it and never completing the connect request. An example of
such publisher is the Wowza server.

This patch adds a timeout of 0.1 seconds to the wait for the bandwidth
negotiation packets from the client. If it is reached, the server will
use the default bandwidth and resume the connection as usual.

Also, initialize the _nextInterval private attribute of the decoder,
which was only initialized after receiving the bandwidth negotiation.
Release 0.1.1.6

* Make handshake less strict with ts and payload
* Implement onStatus and onHeaderData methods
* Don't require client's BW negotiation to connect