liblogging is an easy-to-use, cross-platform library for RFC 3195-style logging. liblogging is an easy-to-use, cross-platform library for RFC 3195-style logging. It has a very simple API which takes out all complexity of the new BEEP-based RFC 3195 syslog standard. liblogging supports RAW and COOKED profiles as well as initiators and listeners.liblogging takes a different approach. It is a library specifcally created to talk syslog, NOT general BEEP. It provides just the bare functionality needed for syslog, nothing else.Consequently it is very slim. The authors hope that this will enable developers of even low-powered devices to adopt the library and provide reliable syslog logging.This library has been named liblogging because it may eventually contain code for additional logging methods in the future (like "plain" UDP syslog, 3195 COOKED and syslog-sign).This library compiles under a variety of platforms. It is originally developed and maintened under Win32. It is frequently ported and tested on Red Hat Linux.These are the platforms (in this order) we have the most confidience in the library on. Others may (though unlikely) show unexpected behaviour.This documentation file here is NOT up to date. However, it will provide you a good overview of the overall design and many specifics. To get the totally right details, please see the respective modules' documentation.Please note that the SEQ handling described below for the listener part is NOT YET implemented - but it is still on the list. As such, the server API should be considered unstable.If you base a server on liblogging, please be prepared to update your server to make it work with future versions of liblogging. Of course we try to keep the impact as low as possible, but that's not a guarantee!The client side API is stable and changes should not be necessary for future releases (except, of course, you would like to use new features).Design Goals:The overall mission of liblogging is to provide a small, easy to use library that will work as an enabler for reliable syslog.There are a number of design goals:· self-containedNo additional libraries shall be needed· low ressource consumptionMemory and CPU usage should be kept to a minimum so that the lib can also be used on low-powered devices· thread-model agnosticNo specific threading model is needed for this library. Everything can be done from a single thread, BUT the library is thread-safe so that it can be called from multiple threads concurrently.· extensible Even though the initial design includes a very limited feature set, liblogging should be able to be extended easily.· portabilityThat's a hard one. liblogging is developed under Win32. While we take reasonable care to make it portable, we only know this once ports have actually been done.Limitations:· tuning profiles are not supported· only 2 channels (channel 0 and 1 syslog channel) are supported· at this time, only the RAW profile is supportedThe file architecture.c does NOT contain any code - it is solely used to provide this documentation.What's New in 0.7.0 Stable Release:· Liblogging now uses autotools and creates a standard system library under Linux.· The is necessary to do a "normal" build under Linux.What's New in 0.7.1 Development Release:· The include structure was changed and a missing include was added. The package name was incorrect and has been fixed.