Re: [cpp-netlib-devel] Insights to the Message Class and Network Routines

[Glyn M. <gly...@gm...>]

Peter,

On 23 May 2007 00:49:24 +0200, Peter Simons <si...@cr...> wrote:

> > Is it your intention to use this for boost.network too?
>
> No. My preference would be that logging is the responsibility of
> the users of this library. With the exception of debugging, I
> wouldn't know what kind of log messages a networking library
> would need to write. Providing functions that pretty-print data
> structures into strings, say an Apache-style access log entry, is
> one thing, but actually writing these strings to some output
> device is another thing. How to do that is a problem ::main()
> should solve.
>
> Does that sound reasonable?



 Yes.  I think more generally its important at this stage to determine
clearly our policies w.r.t. things like logging, thread-safety, security
because we have to ensure that we don't hinder boost.network users from
creating what Dean described as "Custom Web Services".  Someone is always
going to have, for example, complex logging requirements.  Do we just
provide a minimal system and say "X, Y and Z is up to you" or is it possible
to anticipate as far as possible what library users might need?  I'd prefer,
if possible, the former and I think everyone agrees with this, but it does
require that we be careful.

Forgive the sometimes basic questions, I am not as experienced with C++
networking as other people on this list and I'm trying to understand how
this will work conceptually.

G