- From: <piranna@gmail.com>
- Date: Wed, 16 Oct 2013 17:47:03 +0200
- To: Martin Thomson <martin.thomson@skype.net>, Luis López Fernández <luis.lopez@urjc.es>
- Cc: "Anniruddh Koppal (Persistent Systems Ltd.)" <v-ankopp@microsoft.com>, "public-orca@w3.org" <public-orca@w3.org>
> For A and B to talk, messages need to be exchanged between the two before a direct path can be established. This has to happen in both directions. It's not possible for A to send messages to B without B being able to also send messages to A. > 1. B open a listening connection endpoint 2. B connect to STUN server and notifies about the listening connection endpoint 3. STUN server sends connection data to B 4. B send connection data to A over a signaling channel 5. A receives B connection data 5. A open a listening connection endpoint 7. A connect to STUN server 8. STUN server sends connection data to A 9. A send connection data to B over B listening connection endpoint 10. B receives A connection data Is that not possible? With plain BSD sockets seems to be easy, since A and B has open the ports from inside their sides (so NATs and firewalls allow them) and the STUN server has notified them about their external IP and ports... Is there any point that I have missed about how it works? -- "Si quieres viajar alrededor del mundo y ser invitado a hablar en un monton de sitios diferentes, simplemente escribe un sistema operativo Unix." – Linus Tordvals, creador del sistema operativo Linux
Received on Wednesday, 16 October 2013 15:47:51 UTC