> I would even say it's the minority of cases where NAT problems can be > solved.
Check the last few messages in the "My IP address" thread on SJIG, particulary the post made by Jesper Krogh.
Checked and read already. Thanks for the hint again. As Jesper clearly points out, there are NATs which don't support this approach.
True.. but if it works with linux (the page is from before the 2.4 NAT implementation but there's a good chance it will) and with windows internet-sharing you've probably got the majority of cases where your NAT problems are solved. (Still provided you get the external IP address of your gateway from somewhere).
It's not a bad idea anyway to use UDP for voice data in a lot of cases, even if you're in conference mode.
UDP is ok if it works. Anyway there must be a central server to solve all those other issues. The discussion's not about UDP or TCP it's about P2P or central server. and p2p is simply not practical - due to encoding/decoding delays, traffic restrictions on client side, etc.
Both P2P and server-side solutions (espc. in the case of conferencing). For a central server it'd still be nice to have a UDP solution, espc. once we take it beyong voice and add video, start thinking about multicasting, etc.
_______________________________________________
jdev mailing list
[EMAIL PROTECTED]
http://mailman.jabber.org/listinfo/jdev
