On Fri, Aug 10, 2012 at 10:55 PM, Ross Finlayson <[email protected]> wrote: > I would like to know if that would be interesting to make all RTSP > requests handling in RTSPServer session-aware; an example of flow would > be, for a request XXX currently unaware of session (OPTIONS for > instance) > > > No, because the "OPTIONS" command - for listing the RTSP commands that the > server supports - applies to the server as a whole, rather than to a > particular session. > > If you want to redefine the handling of the "OPTIONS" command, then the way > to do this is to subclass "RTSPClientConnection" (not "RTSPClientSession"), > and reimplement the "handleCmd_OPTIONS()" virtual function.
That's what I did, and I put in it additional parsing code for the Session header and could retrieve the corresponding session with a Lookup. Thanks anyway, Lionel > > > Ross Finlayson > Live Networks, Inc. > http://www.live555.com/ > > > _______________________________________________ > live-devel mailing list > [email protected] > http://lists.live555.com/mailman/listinfo/live-devel > _______________________________________________ live-devel mailing list [email protected] http://lists.live555.com/mailman/listinfo/live-devel
