|
From: | John Ogness |
Subject: | Re: [Dazuko-devel] Comments on TAF |
Date: | Mon, 28 Mar 2005 18:48:15 +0200 |
User-agent: | Mozilla Thunderbird 1.0 (X11/20050313) |
Calin A. Culianu wrote:
What about something like: dazukoAddExcludeEvent(struct dazuko_access *);Here an actual event is specified that should be used as an exclude mask. You could specify just a path, in which case it is identical to dazukoAddExcludePath(), or you could specify many attributes that are combined to create a mask.However if you think of it another way, perhaps masking IN is also useful in some situations. For instance, what if you wanted only events from a certain UID? Or from a certain PID? Starting with a mask that excludes everything, then explicitly masking in UID XXX could be useful to some apps that use dazuko (like mine! ;) ).
Hi,I would handle masking in and out in a similar fashion to how paths are currently handled. In other words:
dazukoAddIncludeEvent(struct dazuko_access *); dazukoAddExcludeEvent(struct dazuko_access *);where exclude has priority over include and by default no events are sent (like it is now with paths). This would make dazukoAddIncludePath() and dazukoAddExcludePath() obsolete (these are just special cases of the above functions).
I am *really* starting to like this and I have already thought about how it can be implemented in Dazuko. It should be quite simple, actually. I may push this in before the 2.1.0 release, because I don't want any API changes between 2.1.0 and 2.2.0.
John Ogness -- Dazuko Maintainer
[Prev in Thread] | Current Thread | [Next in Thread] |