Got an interesting bug I'm digging into currently.

In Ruby I've written analogs to the direct_* and simple_ send/recv
example apps. The simple versions all work well and can interact with
Python as expected.

However, the direct_recv.rb example isn't.

When the container starts listening for incoming direct connections, I
see
the following frames come in when the simple_send.rb client (or Python
analog) connects:

<- @open(16)
<- @begin(17)
<- @attach(18)

But what I don't see is the outgoing connection connections that occurr
in the Python version:

-> @open(16)
-> @open(17)
-> @open(18)

So the client connects but the flow never begins between the two. I'm
digging into the acceptor code but don't see where Ruby is behaving
differently from Python.

Any suggestions?

-- 
Darryl L. Pierce, Sr. Software Engineer @ Red Hat, Inc.
Delivering value year after year.
Red Hat ranks #1 in value among software vendors.
http://www.redhat.com/promo/vendor/

Attachment: pgp4bxwIzS6qx.pgp
Description: PGP signature

Reply via email to