summaryrefslogtreecommitdiffstats
path: root/common/elapi/configure.ac
Commit message (Collapse)AuthorAgeFilesLines
* ELAPI Compatibility code for getifaddr()Dmitri Pal2009-10-161-0/+3
| | | | | | | | | | Addreses ticket #94 Actually works pretty well. To try use --enable-compat when build ELAPI. It will use compatibility code instead of getifaddr(). The trick in the elapi_ioctl.h with memory allocation is taken from Stevens book.
* ELAPI Adding file provider and CSV formatDmitri Pal2009-09-081-0/+2
| | | | | | | | | | | | | | | | | | | | | This patch creates the infrastructure for logging of the event from the top of the interface to the bottom. It is a start. A lot of functionality is left aside. The attempt of this patch is pass event from caller of the ELAPI interface via targets to sinks then to providers and do serialization creating entity that is ready to be written to a file. It also implements more specific provider related configuration parameters. Also it addresses couple suggestions that were brought up against previous patch. ELAPI Correcting issues This patch addresses the issues found during the review of the previous patches and addresses ticket #166.
* configure cleanupsSumit Bose2009-09-031-1/+1
| | | | | - replaced mailing list address - let sssd base components read version from VERSION
* ELAPI: Adding concept of targetsDmitri Pal2009-08-201-0/+2
| | | | | | | | | | | | | | | | | | | | | | | | | The targets are the destinations which caller wants to send the events to. The sinks are now on the second level under targets and constitute a so called fail over chain for a target. Such approach eliminates the need for complex routing function. The dispatcher keeps the list of targets in a collection. The element in the collection is the target context. Also gispatcher keeps the list of the sinks in a separate collection. Each target context has a list of the sinks associated with this target. But those are just pointers (at least for now) to the sinks form the list kept by dispatcher. I had to add some internal debug callbacks to be able to see that all the internals of the dispatcher are actually in order. See the conttent of config file for more comments. Also see information posted on SSSD wiki. https://fedorahosted.org/sssd/wiki/WikiPage/ELAPIInterface
* ELAPI Next round of functionality - logging part of the interfaceDmitri Pal2009-08-121-0/+6
| | | | | | | | | | | a) Added the main logging interface which allows creating dispatcher and logging messages or events. Can't actully log anything yet since the sinks are stubbed out. b) Made default template be a part of the default dispatcher. c) Updated UNIT test. d) Some of the calls are stubbed out but they are there to indicate where next round of work will be.
* ELAPI First part of the interfaceDmitri Pal2009-07-151-0/+26
This is just a part of the interface, a beginning. Most likely some of the functions will be altered but it is a starting point. For example in future there will be a way to override some of the parts of the default template using the application configuration file. Removed obfuscation of the data types based on discussion with Simo.