Type: Feature Request
Status: Open (View Workflow)
Affects Version/s: None
Fix Version/s: None
Similar Issues:Show 10 results
NETTY-284 RTSP support on top of HTTP NETTY-153 RTP/RTCP/RTSP Support NETTY-316 RtspResponseDecoder does not decode a RTSP response if Content-Length header is absent. NETTY-94 Base64 codec NETTY-345 HttpChunkAggregator doesn't support retrieving trailing headers NETTY-346 ReplayingDecoderBuffer doesn't support array() NETTY-236 support the half socket close NETTY-6 Add String support to ChannelBuffer NETTY-101 ObjectDecoderInputStream.readObject() discards data and throws a StreamCorruptedException. NETTY-175 Large data transfer
Anton Sherstiuk wrote in
I'd like to request a further feature from RTSP protocol that would be nice to have in Netty.
RFC 2326 for RTSP in its section 10.12 describes a method of interleaving binary data in RTSP stream. Those data may be sent from server to client or vise versa. The format is very simple:
> Stream data such as RTP packets is encapsulated by an ASCII dollar
> sign (24 hexadecimal), followed by a one-byte channel identifier,
> followed by the length of the encapsulated binary data as a binary,
> two-byte integer in network byte order. The stream data follows
> immediately afterwards, without a CRLF, but including the upper-layer
> protocol headers. Each $ block contains exactly one upper-layer
> protocol data unit, e.g., one RTP packet.
Although the existing RTSP codec is easy to extend to support interleaved data, it would be great to have such an extension provided natively. Is it realistic to have the extended codec in 3.2.0?