Khaos :: KhACL

[eluser]esra[/eluser]
Adam... I did something similar, including changing the varchar data types to a maximum of 254. MSSQL is one database server that needs this limit as a basic a requirement. Any database server running on Windows (and possibly the ODBC driver) needs this requirement. The reasoning has more to do with the number of bits per byte (i.e., using even multiples of bits per byte) as supported by a computer's microprocessor architecture.

It's safer to use the MySQL INNODB engine because referential integrity is in effect when foreign keys and unique keys are used, preventing stray data from originating in a table if a database server has a catastropic crash in the middle of a table update. Based on foreign key and unique key relationships, the INNODB engine can recover from such a crash by reconstructing the data based on the constraints established by those indexing keys. Performance differences between MyISAM and INNODB probably favors MyISAM because the INNODB engine needs to do more to provide more features and safer data integrity.

neophyte... I have been integrating your acl, caching, and event manager solutions into an application update currently underway. The thought struck me that if the event manager is added to the mix, it might be possible to add some abstraction to authentication at the application level, allowing multiple authentication schemes to be applied based on different plugins. That is, creating a generic api for authentication and writing plugins for that api. Do you think this is feasible?