Dispatches messages to one or more outputs

Edit Package perl-Log-Dispatch

This module manages a set of Log::Dispatch::* output objects that can be
logged to via a unified interface.

The idea is that you create a Log::Dispatch object and then add various
logging objects to it (such as a file logger or screen logger). Then you
call the 'log' method of the dispatch object, which passes the message to
each of the objects, which in turn decide whether or not to accept the
message and what to do with it.

This makes it possible to call single method and send a message to a log
file, via email, to the screen, and anywhere else, all with very little
code needed on your part, once the dispatching object has been created.

Refresh
Refresh
Source Files
Filename Size Changed
Log-Dispatch-2.42.tar.gz 0000048798 47.7 KB
perl-Log-Dispatch.changes 0000011862 11.6 KB
perl-Log-Dispatch.spec 0000002748 2.68 KB
Revision 29 (latest revision is 47)
Stephan Kulow's avatar Stephan Kulow (coolo) accepted request 250613 from Stephan Kulow's avatar Stephan Kulow (coolo) (revision 29)
- really remove Log-Dispatch-old_Test-More.patch

- updated to 2.42
 - Added a Log::Dispatch->clone() method. This returns shallow clone. The
   outputs and callbacks are shared, but changes to outputs and callbacks in
   the clone do not affect the original, or vice versa.
 
 - Added Log::Dispatch->outputs() method. This returns all the output objects
   in a dispatch object.
 
 - Added Log::Dispatch->callbacks() method. This returns all the callback subs
   in a dispatch object.
 
 - The Syslog output now calls Sys::Syslog::setlogsock() every time a message
   is logged, since something else could have called it in between logging two
   messages.
 
 - Added a lock parameter to the Syslog output. If this is true, then logging
   is done in the scope of a per-thread lock. Reported by Cedric Carree and
   Franck Youssef. RT #67988 and #85013.
 
 - Replaced Class::Load with Module::Runtime.
Comments 0
openSUSE Build Service is sponsored by