This can happen, though only if both your input source and your output sink
(and any filters in-between) are synchronous. E.g, if your input source is a
file on Windoze (where file reading has to be synchronous), and your output
sink is also a file. (It should *not* happen if your output sink is a
"RTPSink".)
The way to overcome this is to find one place in your code (your own code, not
the supplied source code!) that calls
afterGetting(this);
and replace this with:
envir().taskScheduler().scheduleDelayedTask(0, (TaskFunc*)afterGetting,
this);
so that you'll return to the event loop rather than getting into a recursive
call.
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
