Hi Cristian.
since it's ok for you I'm putting the developer mailing list in CC.
In data lunedì 27 luglio 2009 16:52:31, Cristian Bacchi ha scritto:
> I'm curious about a consequence of this your innovation
>
> It seems that this propagation of collection-configuration works
> "only" for the on-the-fly elaboration. In fact you speak about
>
> search_engine …:
> > In order to implement this we could improve the
> > search_engine.RestrictedCollectionDataCacher via a queue with this
> > algorithm.
> >
> > 1) all the explicitly restricted collection are read from the db.
> > 2) the cache is populated with their simple name
> > 3) all the real children of these collection are put in a queue toghether
> > with the restriction of the parent.
> > 4) a collection is taken from the queue with the corresponding parent
> > restriction.
> > 5) the collection restriction (i.e. the father restriction plus
> > eventually the collection restriction itself) is cached
> > 6) all the children are put in the queue with the corresponding
> > calculated restriction
> > 7) back to 4)
>
> …and you mention acc_authorize_action() function.
> (…It sounds very good for my ears, since I'm so involved in the
> problem of filtering the functions on the fly, on the base of the
> users-rights).
> BUT…
Well, that's the first approximation solution I'm proposing to this problem.
To do this on the fly (or almost since it would really be done upon
search_engine module loading, and subsequently cached). Another solution can
anyway be found if necessary :-)
> > When checking if a user is authorized for a collection (i.e. everywhere
> > acc_authorize_action(viewrestrcoll) is used), this should be expanded to
> > checking all the restrictions, from the father to the child, by
> > exploiting the cache.
>
> …I'm wondering: what about the information shown into the "WebSearch
> Admin" interface?:
> if I'll go to manage a child-collection (of a parent with
> restriction), I'll se It restricted or not?
> (probably my deduction is wrong… ;-)
Good point. If we go for implementing all and only what is written in the
Savannah Task, then the WebSearch admin interface wouldn't know about any
inheritated restriction. Already now, indeed, since the collection restriction
is now moved to the WebAccess framework, in the WebSearch admin interface we
can simply know whether a collection is restricted, but not how it is
restricted. Infact we might as well add to this panel an additional
information regarding any inherited restriction. I will updated the Savannah
task accordingly.
> Thanks for your attention
> Cheers :-)
> Cristian
You're welcome! Thank you for the quick feedback :-)
Cheers,
Samuele
--
Samuele Kaplun ** CERN Document Server ** <http://cds.cern.ch/>
