Hi all,
The current "security policy" abstraction in BFG is a bit brittle because it
conflates authentication and authorization APIs. Thus we get things like
"RepozeWhoIdentityInheritingACLSecurityPolicy" and
"RemoteUserInheritingACLSecurityPolicy".
I'd like to tease apart the bits of the cur
2009/5/25 Chris McDonough :
> So to the end of breaking them apart, I just wrote up a bit of science fiction
> in code form. Could you take a look at the below and let me know what you
> think?
It's very clear.
In terms of style, for interfaces that represent would-be adapters,
how do you feel
