David Medinets wrote:
I did some developmental work with ACL and large tables at a previous
company. However, I did not use ACEGI. I didn't know about ACEGI at
the time. Instead I used GUID values at keys with various entities
having various permissions to access specific GUiDs. I used
materialized views in Oracle to keep the query response time
managable.
I've also used views at a RDBMS level instead of relying on Acegi
Security to ACL filter very large tables. However, the underlaying
tables which the views used were structured so that I could also use
them with an Acegi Security BasicAclDao implementation. This let me use
the RDBMS where appropriate (large tables) and Acegi Security/Java for
the rest (including managing the ACL entries in the table).
Cheers
Ben
-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems? Stop! Download the new AJAX search engine that makes
searching your log files as easy as surfing the web. DOWNLOAD SPLUNK!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=103432&bid=230486&dat=121642
_______________________________________________
Home: http://acegisecurity.org
Acegisecurity-developer mailing list
Acegisecurity-developer@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/acegisecurity-developer
