No subject

are received.

But thanks for the example, I will try to do some thorough amq-protocol gem
code review and compare it to a few other clients like the Java client and
Pika.
-- 
MK

http://github.com/michaelklishin
http://twitter.com/michaelklishin

--20cf300259265d0dd404a8983d15
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

2011/7/21 Tony Garnock-Jones <span dir=3D"ltr">&lt;<a href=3D"mailto:tonyga=
rnockjones%2Brabbitmq at gmail.com">tonygarnockjones+rabbitmq at gmail.com</a>&gt=
;</span><br><div class=3D"gmail_quote"><blockquote class=3D"gmail_quote" st=
yle=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">

<div>I could have sworn I made a pull-request with this commit <a href=3D"h=
ttps://github.com/tonyg/amqp/commit/d92a455dcc6763a4495f512f0d74f667354e5a6=
0" target=3D"_blank">https://github.com/tonyg/amqp/commit/d92a455dcc6763a44=
95f512f0d74f667354e5a60</a> some time ago, but I can&#39;t for the life of =
me find it now. Just FTR. It might be worth comparing with the solution you=
&#39;ve adopted.</div>

</blockquote></div><br>Tony,<br><br>We discovered a separate (although simi=
lar) issue: framing on publishing. From what I see, your patch was for cont=
ent boundary detection when frames are received.<br clear=3D"all"><br>But t=
hanks for the example, I will try to do some thorough amq-protocol gem code=
 review and compare it to a few other clients like the Java client and Pika=
.<br>

-- <br>MK<br><br><a href=3D"http://github.com/michaelklishin" target=3D"_bl=
ank">http://github.com/michaelklishin</a><br><a href=3D"http://twitter.com/=
michaelklishin" target=3D"_blank">http://twitter.com/michaelklishin</a><br>=
<br>



--20cf300259265d0dd404a8983d15--