Thu, 02 Feb 2012 14:33:30 +0100 [datafeed] when checking for deletion using cwentity xml parser, use vid=xml to limit resources consumption
Sylvain Thénault <sylvain.thenault@logilab.fr> [Thu, 02 Feb 2012 14:33:30 +0100] rev 8189
[datafeed] when checking for deletion using cwentity xml parser, use vid=xml to limit resources consumption
Tue, 31 Jan 2012 21:43:24 +0100 [repository] ldap-feed source. Closes #2086984
Sylvain Thénault <sylvain.thenault@logilab.fr> [Tue, 31 Jan 2012 21:43:24 +0100] rev 8188
[repository] ldap-feed source. Closes #2086984 datafeed based source which copy a subtree of the ldap directory into the system database. Authentication still go through ldap though. Pros: * don't need temporary tables and such for multi-sources RQL queries execution * much more flexible to enhance / configure behaviour (you simply have to replace the parser) * run better when ldap isn't reachable Cons: * no more 'on the fly' discovery of users (though a user authenticating itself will be automatically added if it doesn't exist in the db yet) * synchronization may be heavy if there are a lot of users A new cw.server.ldaputils containing code in common between former ldapuser and new ldapfeed sources has been introduced. Also ldapuser source now uses url instead of custom host/protocol option so it looks like a datafeed source (could be improved).
Thu, 02 Feb 2012 14:30:07 +0100 [datafeed] set delete-entities=yes is now safer, by checking each entity actually seems deleted. Closes #2165381
Sylvain Thénault <sylvain.thenault@logilab.fr> [Thu, 02 Feb 2012 14:30:07 +0100] rev 8187
[datafeed] set delete-entities=yes is now safer, by checking each entity actually seems deleted. Closes #2165381 Parsers now have to implement the `is_deleted(extid, etype, eid)` method that should return a boolean telling if the given entity exists in the external source or not.
(0) -3000 -1000 -300 -100 -30 -10 -3 +3 +10 +30 +100 +300 +1000 +3000 tip