interleaving between channels not supported? #97
Description
PyRabbitMQ_recv receives a method-frame, then a header-frame, and then body-frames. If inside the body it receives another method-frame, it returns an error ("ConnectionError: Bad frame read").
The thing is, frames might come from different channels. So that 'erroneous' method-frame might actually be a legitimate start in a different channel. This isn't checked or handled in PyRabbitMQ_recv - maybe amqp_simple_wait_frame_on_channel is supposed to be called instead of amqp_simple_wait_frame for the subsequent frames (after the method)?
Naturally this mostly affects messages with large bodies, since they're split across more frames.