Nico Klasens <[EMAIL PROTECTED]> wrote: 
>    I would prefer a taglib for ccsecurity if it implements some cc specific
>    functionality. The cc taglib can be used in all application pages if the
>    page author wants to do some cc security checking. A taglib makes things
>    explicit.

Security checking can already be done with existing mm:-tags, like
<mm:maywrite <mm:maydelete, which work also for ccsecurity.

It's only security editing functionality which is more specific for
ccsecurity.


>    So the implementation of the abstraction is not final yet and will be done
>    in a project. I hope the dependencies don't make too much assumptions
>    about
>    how the final implementation will look like.

The abstraction itself will remain as it is proposed (hence the hack), only
the calling/instantation-mechanism may be temporary, but should appear in
only few spots, so if the future functions project would decide on it
differently then some adaptions will be made, but this should not (or
perhaps hardly) affect existing code which only provides or uses functions.

So, consicely: I agree here :-)

 Michiel

-- 
Michiel Meeuwissen 
Mediapark C101 Hilversum  
+31 (0)35 6772979
nl_NL eo_XX en_US
mihxil'
 [] ()

Reply via email to