Comment # 1
on bug 9837
from Bill Meier
I've been reviewing packet-osc.c and am fixing various issues.
Taking a quick look at the OSC spec, I note the following:
Quote:
The underlying network that delivers an OSC packet is responsible for
delivering both the contents and the size to the OSC application. An OSC packet
can be naturally represented by a datagram by a network protocol such as UDP.
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.
Unquote;
However, I don't see any code in the OSC dissector to specifically handle OSC
over TCP with the packet size at the beginning of each "OSC packet".
(Using dissect_osc_heur() won't work for OSC over tcp).
It's fairly simple to add to a dissector the handling of a TCP stream and I can
do so.
Some questions:
Is OSC over TCP used in the real world ?
Is there an official IANA TCP port assignment for OSC ? (and/or for UDP ?)
Can you provide a capture with OSC over TCP ?
Thanks
Bill Meier
You are receiving this mail because:
- You are watching all bug changes.
