|
From: Stephen S. <rad...@gm...> - 2008-12-17 21:00:02
|
Hi, Last night I was experimenting with the TCP implementation in LibLo. Currently LibLo closes connections after a message is received. The spec says, "In a stream-based protocol such as TCP, the stream should begin with an int32 giving the size of the first packet, followed by the contents of the first packet, followed by the size of the second packet, etc." So that tells me it might be better to leave them open, so I tried this. It worked for a single connection, by adding a "connected_socket" member to the lo_server structure, and polling that instead of the "socket" member. However, I quickly realized that this would mean that lo_server would need a data structure to track _all_ open sockets. I'll probably play with it a little more this week, but any ideas are welcome. Does anyone have any experience with other TCP implementations of OSC? I'd like it if TCP was useable between different implementations. Steve |