updates based on Review of pull request #394
add nat-friendly remote support option
updates based on review of akka/akka pull request #394
remove quotes and rollback accidental addition of an sbt plugin
Alright! So all that's missing now is tests. Create a couple of multi-jvm tests to make sure it works?
Here's the ticket for this: http://www.assembla.com/spaces/akka/tickets/1552-nat-firewall-for-remote-actors#last_comment
Cool, thanks Viktor, will create some tests.
tweaks per Viktor
add multi jvm test for nat
First pass at testing...thoughts?
add check for matching system names in nat support, and add negative …
…tests to spec
I thought about this some more, and I think I might have gotten carried away here.
Wouldn't we be able to solve the problem by just defining a global address and a local address? So you bind to the local address and you receive things going both to the local and the global address?
Or is there a case where you'd need multiple public addresses? And what about the promiscuous mode, does that make sense in a real-world setting? (accepting any inbound message)
simplify to public-addressses copnfig only
Clsoing this pull request since Scott & I agreed this could be solved by having the notion of a global and a local address, but it needs to be carefully implemented so that it covers all bases (Addresses are tricky beasts to say the least)