[Live-devel] about the rtsp session using testOnDemandRTSPServer and mplayer

[김종성]

Hi Fangweiwei,

It's not related to testOnDemandRTSPServer. It seems that you're using the
VideoLAN client as a RTSP client, right? The VLC requests DESCRIBE using a
port, and requests other requests using another port. Even if you're not
using the VLC, it's a problem of the RTSP client.

However, the real problem is that RTSPServer makes a
RTSPServer::RTSPClientSession class instance for the OPTIONS request, but
does not delete it. Another RTSPServer::RTSPClientSession instance handling
the other RTSP requests is always deleted properly.

-----Original Message-----
From: live-devel-bounces at ns.live.com [mailto:live-devel-
bounces at ns.live.com] 
Sent: Saturday, October 16, 2004 9:41 PM
To: live-devel
Subject: [Live-devel] about the rtsp session using testOnDemandRTSPServer
and mplayer

Everyone:
    Hi！
    I have a simple question, I use the "testOnDemandRTSPServer" to set up
a RTSP server, and I use mplayer as a client. But I find in the procedure:
in the  TCP control packets, the "OPTIONS" head use a port,and the other
uses the next available port. but I want to use it to support an
experiment, and I need them to be only one port. that is, all the tcp
control packets using a single port.

    So how can I edit the source code? can you help me?

	

 				

　　　　　　　　Fangweiwei
　　　　　　　　fangweiwei at tom.com
　　　　　　　　　　2004-10-16



_______________________________________________
live-devel mailing list
live-devel at lists.live.com
http://lists.live.com/mailman/listinfo/live-devel