Hi Ross,
Thank you for long reply. I understand how UsageEnvironment works and I also
know how to derive and re implement operator virtual functions.
Having said all this, I do admit, though, that the
diagnostic/debugging output in the provided code is a bit
inconsistent right now
I'd
I think proper logging is vital part of any non-trivial code. I'm willing
to cooperate with you to introduce it in live555 library.
No. Logging is necessarily application specific.
Then why do you ever have it in the library? Either get rid of it completely
or do it correctly.
As I
Hi Ross,
attached please find patch which enables logging levels. It is diff against
live.2010.06.22. It is tested.
Please let me know whether you accept this patch or if it should be improved
or if you deny it (I'd like to know why in this case).
Motivation:
There are many calls in form
There are many calls in form envir() something; or similar. These messages
are either emitted or could be completely disabled by subclassing
[Basic]UsageEnvironment.
The intention of the UsageEnvironment virtual base class is to
allow various environment and application-specific custom
