title: Should I use WebRTC or Websockets (and Socket.io) for OSC communication
body: <p>I am working on an application that will send OSC control messages, which is, as I understand a datagram packet, from a web page to an OSC Receiver (server), such as Max/MSP or Node or any other. </p>
  
  <p>I know typically UDP is used because speed is important in the realtime/ audio visual control work done with OSC (which is also the work I will be doing), but I know other methods can be used.</p>
  
  <p>Right now for instance, I am sending OSC from the browser to a node.js server (using socket.io), and then from the node.js server to Max (which is where I ultimately want the data), also using socket.io. I believe this means I am using websockets and the delay/latency has not been bad.  </p>
  
  <p>I am curious though, now that WebRTC is out, if I should place the future of my work there. In all of my work with OSC I have always used UDP, and only used the Socket.io/Websockets connection because I didn't know about WebRTC.</p>
  
  <p>Any advice on what I should do. Specifically I am interested in <br><br>
  1. How I could send OSC messages from the browser directly to an OSC server (as opposed to going through a node server first)<br><br>
  2. If I should stay with the Node/Socket.io/Websocket method for sending OSC data or should I look into WebRTC?</p>