I like to think of it more as process-driven permission vs artifact
driven permissions, because the "permission string" is defined to
match a specific process. Other than that I think we finally agreed on
something.. Ha! :)
On May 4, 2009, at 1:55 AM, Adrian Crum wrote:
--- On Sun, 5/3/09, Andrew Zeneski <andrew.zene...@hotwaxmedia.com>
wrote:
The question I believe now is, which is better? I
personally think in terms of processes which is why what I
proposed was all process based. However, artifact based may
be more granular, but possibly too granular. If I understand
this right, artifact based we could potentially have
different access requirements for every single
form/screen/service/entity/etc; where in a process based
system the developer would define the processes as part of
the application and these processes could be shared across
common artifacts (forms can share with screens that share
with services, etc).
Does this sound like a fair assessment?
Yes it is. It boils down to permission-driven permissions, versus
artifact-driven permissions.
-Adrian
