...one of the most highly
regarded and expertly designed C++ library projects in the
world.
— Herb Sutter and Andrei
Alexandrescu, C++
Coding Standards
boost::log::sinks::unlocked_sink — Non-blocking logging sink frontend.
// In header: <boost/log/sinks/unlocked_frontend.hpp> template<typename SinkBackendT> class unlocked_sink : public basic_sink_frontend { public: // types typedef SinkBackendT sink_backend_type; // Sink implementation type. typedef shared_ptr< sink_backend_type > locked_backend_ptr; // Type of pointer to the backend. // construct/copy/destruct unlocked_sink(); explicit unlocked_sink(shared_ptr< sink_backend_type > const &); // public member functions locked_backend_ptr locked_backend(); void consume(record_view const &); void flush(); };
The sink frontend does not perform thread synchronization and simply passes logging records to the sink backend.
unlocked_sink
public
construct/copy/destructunlocked_sink();
Default constructor. Constructs the sink backend instance. Requires the backend to be default-constructible.
explicit unlocked_sink(shared_ptr< sink_backend_type > const & backend);
Constructor attaches user-constructed backend instance
Parameters: |
|
||
Requires: |
backend is not |
unlocked_sink
public member functionslocked_backend_ptr locked_backend();
Locking accessor to the attached backend.
Note | |
---|---|
Does not do any actual locking, provided only for interface consistency with other frontends. |
void consume(record_view const & rec);
Passes the log record to the backend
void flush();
The method performs flushing of any internal buffers that may hold log records. The method may take considerable time to complete and may block both the calling thread and threads attempting to put new records into the sink while this call is in progress.