On Sat, Aug 11, 2012 at 2:15 AM, Ross Finlayson <[email protected]> wrote: > 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. > > > But there's no guarantee that an "OPTIONS" request will even contain a > session header. And even if it does, there's nothing session-specific that > you could/should be doing to handle it, because the only thing an "OPTIONS" > response should contain is a list of request names that the server handles. > And that has nothing to do with session-specific state.
I agree with you. But I am working with a kind of proprietary RTSP superset which need this (they use OPTIONS to keep-alive sessions), and I am not responsible for these choices. :) 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
