Is there any interest in a Group of library like to Application System!
I am proposing before a Log library in model of Log4cxx, but my plan is provide a full application system that will have: * Log System (Log4cxx Model) * Application System (Windows Service, Unix Daemon and Usual Application) -> Process Management (I don't know?) * Plugin System (service model): dynamically late bind extension. This will provide modular functionality that can be loaded in applications. For sample a service that can be loaded in application container, or a skin loaded in Client (MP3) Application. To illustrate: A developer that need create a server application will do: 1) Extend for "boost::application::server" and in this it use boost::log. (here if app is a Win32 then it have a Windows Service, or a daemon in unix) 2) To create service (modular application) he extend of "boost::service" to create a service and plug this service in runtime on "boost::application::server". Note that: Application can be configured using Boost.Program_options for sample. We can use Boost.Log to log, or (I don't know) we can buid Log4 model on top of Boost.Log? What Boosters think? Boosters think that "this kind of lib" is very specific, and violate: "The library must be generally useful and not restricted to a narrow problem domain." or this kind of system is relevant to boost. Please let me know the correct way to follows! Anyone that want participate is welcome! Ps: Ps: We already have some discussion in "Log Lib" topic! Thanks
On Wednesday, January 04, 2012 08:42:55 Renato Tegon Forti wrote:
We can use Boost.Log to log, or (I don't know) we can buid Log4 model on top of Boost.Log?
Boost.Log was deliberately designed in a different direction from log4cxx and similar libraries. However, one can come quite close to what log4cxx provides with Boost.Log by means of channels and filtering. For instance, you can consider channel name (which is a string) as a logger name, in terms of log4cxx, and arrange filters so that log records from this logger only pass to particular sinks.
Hi Andrey, Thanks for your response! What is status of your lib? Do you need any help? -----Mensagem original----- De: boost-bounces@lists.boost.org [mailto:boost-bounces@lists.boost.org] Em nome de Andrey Semashev Enviada em: quarta-feira, 4 de janeiro de 2012 08:55 Para: boost@lists.boost.org Assunto: Re: [boost] Is there any interest in a Group of library like to Application System! On Wednesday, January 04, 2012 08:42:55 Renato Tegon Forti wrote:
We can use Boost.Log to log, or (I don't know) we can buid Log4 model on top of Boost.Log?
Boost.Log was deliberately designed in a different direction from log4cxx and similar libraries. However, one can come quite close to what log4cxx provides with Boost.Log by means of channels and filtering. For instance, you can consider channel name (which is a string) as a logger name, in terms of log4cxx, and arrange filters so that log records from this logger only pass to particular sinks. _______________________________________________ Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost
Application System is a good addition even if the logging isn't ready. Don't delay releasing because of waiting on the false prerequisite of your additions to an unavailable/unreleased boost logging. Incremental releases is reasonable and preferable to waiting indefinitely on perfection. On 1/4/2012 5:42 AM, Renato Tegon Forti wrote:
I am proposing before a Log library in model of Log4cxx, but my plan is provide a full application system that will have:
...
* Application System (Windows Service, Unix Daemon and Usual Application)
...
To illustrate: A developer that need create a server application will do:
1) Extend for "boost::application::server" and in this it use boost::log. (here if app is a Win32 then it have a Windows Service, or a daemon in unix)
2) To create service (modular application) he extend of "boost::service" to create a service and plug this service in runtime on "boost::application::server".
...
_______________________________________________ Unsubscribe& other changes: http://lists.boost.org/mailman/listinfo.cgi/boost
participants (3)
-
Andrey Semashev -
Jarrad Waterloo -
Renato Tegon Forti