[Live-devel] problems moving to asynchronous rtsp interface
Ross Finlayson
finlayson at live555.com
Sat Nov 26 14:01:57 PST 2011
> But if the callback could use a void* for the first arg, then [...]
You need to abandon this line of thinking. The asynchronous "RTSPClient" interface has been in place - and in use by lots of people - for a year and a half now. It's not going to change (at least, not significantly).
Each response handler callback routine gets a pointer (as its first parameter). It's not a "void*"; instead, it's a "RTSPClient*". But this one pointer is enough to give you all the state you need. Having a second (or third) extra "void*" pointer would be extraneous and unnecessary. If you want to carry around a pointer to some extra state, then you can just do so using a field in your "RTSPClient" subclass.
Ross Finlayson
Live Networks, Inc.
http://www.live555.com/
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.live555.com/pipermail/live-devel/attachments/20111126/b29be490/attachment.html>
More information about the live-devel
mailing list