[Building Sakai] Proposed API change to reduce cost of resources list view

[Jim Eng]

That may be a good solution, but we still need to give the .anon role  
content.read permission for the realm, so then we would be tracking  
this in two tables.  If there's an efficient way that avoids having to  
keep those values in two places and trying to keep them in sync, I  
think we would like to do it that way.

Jim



On Sep 22, 2009, at 2:04 PM, R.P. Aditya wrote:

> On 2009-09-22, Jim Eng <jimeng at umich.edu> wrote:
>> there are other variations) for which there are entries in the
>> sakai_realm_rl_fn table where the role_key identifies the anonymous
>> role and the function_key corresponds to "content.read". The result
>> would be a list of realm identifiers.
>
> I haven't run the stats yet but I'd suspect that *most* resources are
> not public. If that is the case, then having a separate table to just
> list the public resources will likely be your best bet, esp. if it is
> going to be consulted so often.
>
> Your updated api call could then see if that table exists and if not,
> revert to using your suggested method with the like.
>
> Adi
>
> _______________________________________________
> sakai-dev mailing list
> sakai-dev at collab.sakaiproject.org
> http://collab.sakaiproject.org/mailman/listinfo/sakai-dev
>
> TO UNSUBSCRIBE: send email to sakai-dev-unsubscribe at collab.sakaiproject.org 
>  with a subject of "unsubscribe"
>
>