Bidirectionnal Thrift in scala about bidithrift HOT 5 CLOSED

Very cool! Your Scala implementation is much cleaner. Now I'm tempted to write a version in Erlang to see how it compares to Scala =)

from bidithrift.

Haha programming language war :P.

I think it will be pretty similar, because most of the scala code are actors.

about issues/1 are you using thrift 0.6.0 ? I think it's the only version that work with oneway rpc.

from bidithrift.

Unfortunately, I can't remember which version of thrift I was using. It was
a very old version, as that code sample is from about three years ago,
IIRC. At the time thrift wasn't available in the main maven repo. I should
update the code.

On Fri, Oct 12, 2012 at 10:34 AM, Guillaume Massé
[email protected]:

Haha programming language war :P.

I think it will be pretty similar, because most of the scala code are
actors.

about issues/1 #1 are you
using thrift 0.6.0 ? I think it's the only version that work with oneway
rpc.

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/2#issuecomment-9384112.

from bidithrift.

Great 👍 as I mention version 0.6.0 work fine and you can get libthrift from main maven repo.

In the article you say:

The nice thing about this method is that you don't have to establish two connections, so you can get around the >firewall issues others have mentioned.

I dont get this. I think the client still have to have an firewall outbound rule for port XYZ.

from bidithrift.

On Sat, Oct 13, 2012 at 10:42 AM, Guillaume Massé
[email protected]:

Great [image: 👍] as I mention version 0.6.0 work fine and you can get
libthrift from main maven repo.

In the articlehttp://joelpm.com/2009/04/03/thrift-bidirectional-async-rpc.htmlyou say:

The nice thing about this method is that you don't have to establish two
connections, so you can get around the >firewall issues others have
mentioned.

I dont get this. I think the client still have to have an firewall
outbound rule for port XYZ.

The client still has to allow an outbound connection, but you don't have to
punch a hole in the firewall for a port to listen for an inbound
connection. The client establishes the connection and uses it for
bidirectional communication, rather than one port for inbound communication
and another port for outbound communication (as some had suggested at the
time that I wrote the article).

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/2#issuecomment-9406750.

from bidithrift.