## Changes between 2.1.0 and 2.2.0 (unreleased)
### Timestamps are Encoded as 64-bit Unsigned Integers
This is a potentially **breaking change**. It is recommended that
all applications that use this gem and pass date/time values in message
properties or headers are upgraded at the same time.
GitHub issue: [#64](https://github.com/ruby-amqp/amq-protocol/issues/64).
Contributed by Carl Hoerberg.
2.0.1
* Support encoding of byte arrays, fixes#58.
* Fix encoding for headers and properties if using nested headers.
* Fix#30 (headers encoding other than ASCII-8BIT).
## Changes between 1.9.x and 2.0.0
2.0.0 has **breaking changes** in header encoding.
### Signed Integer Encoding in Headers
Integer values in headers are now encoded as signed 64-bit
(was unsigned 32-bit previously, unintentionally).
This is a breaking change: consuming messages with integers in headers
published with older versions of this library will break!
### Signed 16 Bit Integer Decoding
Signed 16 bit integers are now decoded correctly.
### Signed 8 Bit Integer Decoding
Signed 8 bit integers are now decoded correctly.
Contributed by Benjamin Conlan.
## Changes between 1.9.x and 1.10.0
### Signed 16 Bit Integer Decoding
Signed 16 bit integers are now decoded correctly.
Contributed by Benjamin Conlan.
## Changes between 1.8.0 and 1.9.0
### Performance Improvements in AMQ::BitSet
`AMQ::BitSet#next_clear_bit` is now drastically more efficient
(down from 6 minutes for 10,000 iterations to 4 seconds for 65,536 iterations).
Contributed by Doug Rohrer, Dave Anderson, and Jason Voegele from
[Neo](http://www.neo.com).
## Changes between 1.7.0 and 1.8.0
### Body Framing Fix
Messages exactly 128 Kb in size are now framed correctly.
Contributed by Nicolas Viennot.
* Frame body on Ruby 1.9+ using bytes, not code points String#slice will only
use byte slicing if the string is considered to be in ASCII.
* Replace broken link with an inline comment
* Adds specs to validate 8bit/16bit signed decoding
* Adds 8bit signed and 16bit signed integers to table decoder
## Changes between 1.0.0 and 1.0.1
### Missing require
`amq-protocol` now makes sure `DateTime` is loaded before trying to use it.
## Changes between 1.0.0.pre6 and 1.0.0.pre7
### AMQ::Settings
`AMQ::Settings` extracts settings merging logic and AMQP/AMQPS URI parsing from `amq-client`.
Parsing follows the same convention amqp gem and RabbitMQ Java client follow.
Examples:
``` ruby
AMQ::Settings.parse_amqp_url("amqp://dev.rabbitmq.com") # => vhost is nil, so default (/) will be used
AMQ::Settings.parse_amqp_url("amqp://dev.rabbitmq.com/") # => vhost is an empty string
AMQ::Settings.parse_amqp_url("amqp://dev.rabbitmq.com/%2Fvault") # => vhost is /vault
AMQ::Settings.parse_amqp_url("amqp://dev.rabbitmq.com/production") # => vhost is production
AMQ::Settings.parse_amqp_url("amqp://dev.rabbitmq.com/a.b.c") # => vhost is a.b.c
AMQ::Settings.parse_amqp_url("amqp://dev.rabbitmq.com/foo/bar") # => ArgumentError
```
### AMQ::Protocol::TLS_PORT
`AMQ::Protocol::TLS_PORT` is a new constant that contains default AMQPS 0.9.1 port,
5671.
(This is required by new ruby-amqp package.
amq-protocol is an AMQP 0.9.1 serialization library for Ruby. It is not an
AMQP client: amq-protocol only handles serialization and deserialization.
If you want to write your own AMQP client, this gem can help you with that.
