> -----Original Message-----
> From: David Audrain [mailto:daudrain roundbox.com]
> Sent: Friday, December 01, 2006 9:26 AM Ping
> To: Henry Ping
> Cc: protocol-devhelixcommunity.org
> Subject: Re: [Protocol-dev] RTSP : interleaving
>
> In effect, RTSPClientSession looks to be the one that
closes
> the socket.
> But the it looks like the RTSPTransports objects are
> destroyed after, and these objects are not notified
that the
> interleave connection has been closed.
> This prevents a gracefully close of rtsp connection
with the
> server, as the *shared* socket is closed, transports
can't
> send bye. (with Win32 it would lead to crash because
> CHXSocket: oWrite
will try to access m_pWriteQueue which has
> been freed by CHXSocket::Close).
Sounds like a bug to me.
> The cayenne_1_5_0 does not seem to take in account the
rtsp
> hierarchy you drew.
> RTSPClientSession is the RTSP session and
RTSPTransports are
> the transports.
> Which class represents the RTSP connection?
The hierarchy exists in Cay150:
RTSP Session -> RTSPClientSession(RTSP Connection)
RTSP -> RTSPClientProtocol(RTSP protocol session)
-->Henry
> Thx
> David
>
> Henry Ping wrote:
> > It's the RTSPClientSession.
> >
> > When interleaved, the RTSP session socket can be
shared not only by
> > the RTP&RTCP transports but also multiple RTSP
connections
> to the same server:
> >
> > RTSP Session
> > |
> > -----------------
> > | | |
> > RTSP_0 RTSP_1 ...
> > |
> > -------
> > | |
> > RTP RTCP
> >
> >
> > -->Henry
> >
> >
> >> -----Original Message-----
> >> From: protocol-dev-bounceshelixcommunity.org
> >> [mailto:protocol-dev-bounceshelixcommunity.org] On Behalf
> Of David
> >> Audrain
> >> Sent: Friday, December 01, 2006 7:53 AM Ping
> >> To: protocol-devhelixcommunity.org
> >> Subject: [Protocol-dev] RTSP : interleaving
> >>
> >> Hi All,
> >>
> >> In case of an interleaved RTSP connection,
which component is
> >> supposed to close the socket :
> >>
> >> 1. RTSPClientSession::closeSocket by
calling close on
> m_pSocket or
> >> releasing it.
> >> 2. RTPTCPTransport:one by
releasing m_pTCPSocket.
> >> 3. RTCPTCPTransport:one by
releasing m_pTCPSocket.
> >>
> >>
> >> Thanks,
> >> David
> >>
> >>
> >>
_______________________________________________
> >> Protocol-dev mailing list
> >> Protocol-devhelixcommunity.org
> >> http://lists.helixcommunity.org/mailman/listinfo/pr
otocol-dev
> >>
> >
> >
>
_______________________________________________
Protocol-dev mailing list
Protocol-devhelixcommunity.org
http://lists.helixcommunity.org/mailman/listinfo/pr
otocol-dev
|