|
From: Stephen S. <rad...@gm...> - 2011-11-22 18:31:27
|
On Tue, Nov 22, 2011 at 8:52 AM, Camille Troillard <ca...@os...> wrote: > I think having IPv6 and TCP support in liblo is a real plus. I agree that TCP is a great feature. Would love to discuss if anyone has experience using OSC over TCP, as I haven't actually used it all that much. I would like to know how it compares to other implementations. I have to look more into it but I think there are some further suggestions for how to package OSC over a stream connection in the OSC 1.1 specification. And there is currently extensive discussion of OSC 2.0 happening on the OSC-dev list, but I haven't been following it 100%, however my impression is that there are suggestions for certain transport-level standards. I know that CNMAT has been proposing to always use SLIP encoding to packetize streams, but this is not what liblo currently does. Instead it takes the length-then-body approach. I happen to think that over a reliable connection the latter is better, since it makes memory handling a little easier, but I'd like to maintain compatibility with other libraries. Does LibLo perhaps need an API to set TCP stream options such as which packetizing protocol to use? Steve |