[rsyslog] output plugin calling interface

[Rainer Gerhards]

OK, I uploaded a new document. It is not really clean yet, but much better
than the version from around noon. I think I need at least another hour to
make sure that terminology is used consistently. Most important, it may say
"doAction()" where "processAction()" is more precise (but not always). That's
because my thinking evolved today ;)

Take care of the new state diagram and be sure to understand that it models
an own *action state*, not a batch transaction state (that's different and
for tomorrow ;)).

Rainer

> -----Original Message-----
> From: rsyslog-bounces at lists.adiscon.com [mailto:rsyslog-
> bounces at lists.adiscon.com] On Behalf Of Rainer Gerhards
> Sent: Wednesday, May 06, 2009 6:33 PM
> To: rsyslog-users
> Subject: Re: [rsyslog] output plugin calling interface
> 
> > then it is simpler to do so than it would be to have
> > both the partial retry processing _and_ the output module issueing
commits
> > whenever it wants to.
> 
> 
> Why? If I think about code, it is very hard to beat auto-commits in
> simplicity...
> 
> But I'd better finish the new state diagram and at least part of the
> description, I think I finally found the right model for the lower layer.
> 
> Rainer
> _______________________________________________
> rsyslog mailing list
> http://lists.adiscon.net/mailman/listinfo/rsyslog
> http://www.rsyslog.com