> >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 noted in my > earlier message, you can do it however you want in your > "[Basic]UsageEnvironment" subclass. But I won't be adding any > specific 'logging' functionality to the supplied "LIVE555 Streaming > Media" library code. Yes, I know, i have did it. But it is too coarse for me. Just subclassing does not work for me. I really really need to filter by importance.Using RTSPClient.cpp as example I have no way to decide if that "message" is debug one like envir() << "Opening connection to " ... or just something even less important like envir() << "...local connection opened\n" or somethig informative (more than debug) like envir() << "Sending request: " << cmd << "\n" By the way the last one it the only way to know sent RTSP command from client code as cmd is destroyed before function return. > >Are you willing to incorporate patches? > > Yes - if they fit with the overall architecture of the code. All right, I will try again with something completely different (not logging). Best Regards David Stegbauer This e-mail and any attachment is for authorised use by the intended recipient(s) only. It may contain proprietary material, confidential information and/or be subject to legal privilege. It should not be copied, disclosed to, retained or used by, any other party. If you are not an intended recipient then please promptly delete this e-mail and any attachment and all copies and inform the sender. Thank you. _______________________________________________ live-devel mailing list live-devel@lists.live555.com http://lists.live555.com/mailman/listinfo/live-devel
