I tried reworking some of my code today to use the new asynchronous interface, but ran into a couple problems. First, I do not see a way to set the URL.
The URL is now passed as a parameter to "RTSPClient::createNew()". This makes more sense than (the previous behavior of) passing it as a parameter to the 'describe' operation, because each "RTSPClient" object is intended to bew used for a single stream only.
Second, would it be possible to get a client data pointer on the RTSPClient::responseHandler callback like there is with callbacks for getNextFrame()?
I'm not yet convinced that this is necessary. However, upon reflection, I wonder if it might make sense to pass the "CSeq" value as a parameter to the handler function (along with the "RTSPClient" object), so that the handler function can identify which particular request this handler is for. (Note that each of the command-sending member functions return a "CSeq" value as its result.
How were you intending to use the "client data" value? -- Ross Finlayson Live Networks, Inc. http://www.live555.com/ _______________________________________________ live-devel mailing list live-devel@lists.live555.com http://lists.live555.com/mailman/listinfo/live-devel
