>
> I did not mean "let the user change the
weights", the idea was "use
the
> given order" which would require using multiple
properties of the same
> name (which I understand would require to change the
parsing
mechanism,
> but on the other hand multiple properties of the same
name returning
> BELArray would be a nice feature for WikiTalk in the
end)
>
> Reason why I mention it is rather selfish as we use
our Passport
> system and build on hierarchy models heavily. You are
right; I have no
> idea how important this feature is for other users.
>
Sorry, I probably hazed the topic little Actually I
was working on
my local solution of the FW security when I run into this
thread. My way
is strictly based on properties included in the actual
topics (plus
additional one in namespace definition). As far I understand
the
concept, it may slightly differ here.
BTW, what I wrote about multiple instances on same property
is not
necessary anyway. What about following syntax:
ReadACL: +group:management, -group:production, +user/jvanous
Hmmmm ... when I think about it again and again, I'm getting
convinced
that the original idea of sorting access rules according to
the
described scheme (deny preceding allow, ...) is right and
custom
ordering does not give to it much additional value. I could
live with it
pretty happily )
-honza
------------------------------------------------------------
-------------
Using Tomcat but need to do more? Need to support web
services, security?
Get stuff done quickly with pre-integrated technology to
make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on
Apache Geronimo
http://sel.as-us.falkag.net/
sel?cmd=lnk&kid=120709&bid=263057&dat=121642
_______________________________________________
Flexwiki-users mailing list
Flexwiki-users lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/flexwiki
-users
|