should we fetch all children, rather than only viewable children, when user selects a node in the Resource tree?

Ian Springer ian.springer at redhat.com
Wed Oct 19 20:29:01 UTC 2011


On 10/19/2011 03:57 PM, Jay Shaughnessy wrote:
>
> On 10/19/2011 1:58 PM, Ian Springer wrote:
>> In the else block in ResourceTreeDatasource.executeFetch(), we may 
>> want to consider fetching ResourceLineageComposites, as we do for the 
>> initial data, so that we can display locked nodes for any child nodes 
>> of the selected node that are not viewable. That would allow the user 
>> to select one of those locked child nodes and see its children, which 
>> potentially *could* be viewable. In such a scenario, where the user 
>> has view access to a Resource, but not its parent, the only way they 
>> could currently get to the Resource is by selecting it from one of 
>> the Resource list views.
> Interesting, but my current thinking is that it's probably not worth 
> the overhead.   I think it's OK to go to the resource list view, or a 
> group view, or potentially  a favorite to get to a viewable resource.  
> I sort of like the fact that locked is locked completely.

But it's not locked completely for the Resources loaded on the initial 
tree load is it? For example, if the user goes to a server resource, if 
that server's platform is not viewable to the user, they can still see 
any children of that platform that are viewable (i.e. the viewable 
siblings of the server they originally went to).


More information about the rhq-devel mailing list