Use a std::function callback rather then std::cout to log data

[bamkrs]

I'm using pistache in several projects now and what stressed me is the common use of std::cout's.
This is a example on how to use callbacks for log-messages, with std::cout fallback.

[dgreatwood]

Hi George - Re: Logging, as part of the macOS port additionally logging facilities (look for PIST_LOG_...) were added. Messages are recorded via syslog on Linux and BSD, and os_log in macOS. It is more C-style than C++ ("printf" style vs "<<") but has stack backtrace, function entry+exit tracking, lock on+off tracking, timing and so on. Providing a "<<"-style interface to PIST_LOG might be nice to do at some point. Most of the log messages added are to follow the low-level event and network code. Also, the great majority of messages will show up only from the debug builds. Thanks. Duncan.

…

On Tue, Aug 6, 2024 at 4:02 AM George Sedov ***@***.***> wrote: But pistache already has one logging system in place. Sure, it's underused and somewhat broken (it's not passed to the listener in Endpoint::init), but it's probably better to improve it rather than introduce a whole new callback system. — Reply to this email directly, view it on GitHub <#19 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAFMA2Y66L5SAKJE6MFEUWTZQCULBAVCNFSM6AAAAABMCCUO2OVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDENZRGAYDIOJSGI> . You are receiving this because you are subscribed to this thread.Message ID: ***@***.***>

-- NOTICE: This email and its attachments may contain privileged and confidential information, only for the viewing and use of the intended recipient. If you are not the intended recipient, you are hereby notified that any disclosure, copying, distribution, acting upon, or use of the information contained in this email and its attachments is strictly prohibited and that this email and its attachments must be immediately returned to the sender and deleted from your system. If you received this email erroneously, please notify the sender immediately.  Xage Security, Inc. and its affiliates will never request personal information (e.g., passwords, Social Security numbers) via email.  Report suspicious emails to ***@***.*** ***@***.***>