fixes issue with wrong assumption about binary protocol

[elmacnifico]

the original implementation thought that "size" would describe the
number of elements in the following array while it in fact desribes the
number of bytes that will be in the following array. so any assumption
about the number of elements would be flawed and lead to too many
itterations ending in EOF reading errors

[elmacnifico]

sorry i wanted to pull this into our fork for some refactoring first. but the general problem should be clear ;). so ignore this one if you like, as i may find a more elegant solution.

[elmacnifico]

also the decoding of header tables with nested field-arrays should be tested

[wellle]

In order to reproduce the behavior in question you can use the following small go program. (instructions included)
https://gist.github.com/wellle/5319271

[streadway]

Thanks for the report. The spec is ambiguous about the interpretation of the size field in array packing so I'll also be digging through other client implementations and get some better tests in over the weekend. I plan on using http://golang.org/pkg/io/#LimitedReader in the final implementation.