I was wondering if a better support for privacy consent is needed into the
registry module.
Actually if we want to store such kind of informations we need to define a
custom property into the Entry instance, may be storing into a constant the
property key.
Such approach is obviously:
* unperformant as reading this field needs accessing another table and
searching for entries with a specific value needs a table join
* unflexible as searching for more than one property need a multiple full
join on the properties table
* error prone as the property key may be already in use or mispelled
I thought a bitmask field into the Entry class could solve the problem at
its root as it allows:
* multiple true/false settings for independent levels of privacy
authorizations
* fast and flexible searches
* small size increase as with a short we can handle 16 independent levels
which should be a lot more than actually needed by anyone and it can be
easily increased up to 64
In general the same approach could be used for profiling basing on a
true/false basis...
Waiting for your opinions before opening a feature request on the tracking
system here at SourceForge
--
View this message in context: http://www.nabble.com/Privacy-consent-in-registry-module-tf3485703s17546.html#a9731003
Sent from the SmartWeb Developers mailing list archive at Nabble.com.
|
