On 14 Jan, 2006, at 6:37 pm, Simon Belak wrote:
Kevin mentioned on several occasions (see ticket #313) that he
would like to investigate the possibility of using RuleDispatch.
Yup. And I'm keen to investigate using it. I just need to have some
use cases where adding RuleDispatch enables functionality that
doesn't already exist and which couldn't be added easily without
RuleDispatch.
To be honest, your current work (I do hope I did not come of as
trying to put it down too harshly. If I did, I am truly sorry.)
covers well over 90% of use-cases,
No you didn't sound harsh at all. I'm just trying to get a grasp on
what's desired. I *really* want Identity to solve the majority of the
use cases, and if I'm missing some, I want to know. What exists now
is everything that leapt to mind when I was first writing it.
I simply like generic functions (to put it bluntly, I am just as
biassed as you :)).
I like generic functions too. I think they're cool. One of the things
I'm looking at is using generics to handle ownership. Because
ownership is *so* model dependant, it makes sense to have:
is_owner.when( 'isinstance(obj, MyObj) and identity.user in
obj.owners' )
Although it might be nice to discover a cleaner syntax for us mere
mortals.
It has to be said however that some things could be solved more
elegantly. Here peak.security shines.
Exactly. But what things? Which things need cleaning up? I can't tell
because I'm too close to the code.
--
Jeff Watkins
http://newburyportion.com/
"Advertising directed at children is inherently deceptive and
exploits children under eight years of age."
-- American Academy of Pediatrics
