It turns out the problem was on my side. I was using code based on the C# examples, which used a socket transport, wrapped in a framed transport. But the patch uses a normal socket transport, which was why it was unable to parse the header. Using a TSocket fixed the problem. I have yet to test the patch on the issue extensively, but it looks like it works correctly.
On Thu, Jul 24, 2014 at 1:04 PM, Jens Geyer <[email protected]> wrote: > Hi, > > > Is this feature still planned for Erlang? >> > > Sure it is, and many thanks for your investigations! In the last weeks > there have been some improvements on the Erlang part of Thrift in trunk, > which will find their way into the forthcoming 0.9.2 release. So in a way > that's quite a good timing. I'd recommend to try against trunk (if you > didn't already do that), document your findings and especially the error > messages etc. at said JIRA ticket, and hopefully the Erlang guys will pick > it up. > > Have fun, > JensG > > > -----Ursprüngliche Nachricht----- From: Ninja Ferret > Sent: Thursday, July 24, 2014 6:34 PM > To: [email protected] > Subject: Erlang Multiplexing Server support > > > There's a patch for multiplexing under the issue ( > https://issues.apache.org/jira/browse/THRIFT-2110) but while it's test > program runs to completion (Erlang client and server), it fails when I use > a client written in C# with version 0.9.1. I was able to track a part of > the problem to binary headers, but even with strict read/write turned off, > the server fails to work. Is this feature still planned for Erlang? >
