I realize that it's a really, really hard problem to solve.<div><br></div><div>What I asked with this last message is, "Has anyone considered SIP as a possible solution to this problem?"</div><div>RFC 3261: <a href="http://www.ietf.org/rfc/rfc3261.txt?number=3261">http://www.ietf.org/rfc/rfc3261.txt?number=3261</a></div>
<div><br></div><div>Another possible solution might be the protocol that Jabber uses to establish peer-to-peer file transfers. "Has anyone considered the possibility of using this as a solution?"</div><div><a href="http://xmpp.org/extensions/xep-0096.html">http://xmpp.org/extensions/xep-0096.html</a></div>
<div><br></div><div>I'm not a programmer (per se). I'm not going to learn how to program in Python. I am, however, a problem solver. I'm really, really interested in finding interesting solutions to interesting problems. THIS clearly is an "interesting problem."</div>
<div><br></div><div>I know it's a really really hard problem to solve. I've pointed to two opensource projects that have solved similar problems. </div><div><br></div><div>If this level of usage is outside the parameters of what tahoe-lafs is trying to address, that's fine. I'm just asking.</div>
<div><br></div><div>Thanks,</div><div>Jody</div><div>----<br>- Think carefully.<br>- Contra mundum - "Against the world" (St. Athanasius)<br>- Credo ut intelliga - "I believe that I may know" (St. Augustin of Hippo)<br>
<br><br><div class="gmail_quote">On Fri, Dec 18, 2009 at 9:37 PM, Shawn Willden <span dir="ltr"><<a href="mailto:shawn@willden.org">shawn@willden.org</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
<div class="im">On Friday 18 December 2009 04:43:13 pm Jody Harris wrote:<br>
> Am I to understand this to mean that resolving this issue is not a priority<br>
> for the tahoe development team?<br>
<br>
</div>Well, I can't speak for the "tahoe development team" (whatever that is) but<br>
what I meant is that this is a really hard problem to solve, and it's really<br>
sad that it impedes so much progress.<br>
<br>
As for the solution, there are a lot of different NAT traversal techniques<br>
that address various forms of NAT. What's needed is for someone to do the<br>
research on the tools and techniques that are most applicable, and then take<br>
a shot at adding traversal support to Tahoe.<br>
<br>
Perhaps you'd like to do it? A good place to start might be to find out what<br>
NAT traversal libraries exist and how hard they are to use, and how hard they<br>
are to port to all of the platforms Tahoe runs on. Python libs would be<br>
ideal, but C or C++ libs aren't too bad, as long as they're portable.<br>
<div><div></div><div class="h5"><br>
Shawn.<br>
_______________________________________________<br>
tahoe-dev mailing list<br>
<a href="mailto:tahoe-dev@allmydata.org">tahoe-dev@allmydata.org</a><br>
<a href="http://allmydata.org/cgi-bin/mailman/listinfo/tahoe-dev" target="_blank">http://allmydata.org/cgi-bin/mailman/listinfo/tahoe-dev</a><br>
</div></div></blockquote></div><br></div>