On Wed, Feb 23, 2011 at 02:02:17PM +0000, hyc@symas.com wrote:

...

A URI-based restriction specification could include/exclude based on suffix, filter and listed attributes with a unified syntax.

Yes... But what does the filter *mean* in a modify op? filter on the target entry before it was modified, or after?

Hmm - I was thinking of matching on the *modified attributes* (just their presence, not taking account of value). However, I can see that pre- and post-conditions might matter so:

logrecord <operations> prefilter|changefilter|postfilter <LDAP URL> logignore <operations> prefilter|changefilter|postfilter <LDAP URL> ...

a search op? match the search request's filter, or filter on the search base?

Both if present. Again, I might restrict the filter to matching on the presence of attributes in the filter rather than their actual value.

a compare op?

Whatever works for search should be very close.

Andrew