|
|
|
| The following comment has been added to this issue: |
[ Permlink ] |
|
Author: Georges Racinet
Date: 10/07/07 14:45
Comment:
Thx for report Sylvain,
this refresh() can be necessary, and its caller doesn't have the info to decide whether to trigger it or not.
My take on this is that the various setting methods of providers should maybe set a lazy pointer to the requested page and do nothing besides invalidating the current page.
The first actual use of the getter will then trigger the search/conversion of results, no matter how many calls to refresh() there was in the meanwhile. The latter should maybe called invalidate() but that might introduce a confusion with the invalidate method of ResultsProviderCache.
In any case, all of this should be documented in the interface, so that application code can have a clue of the performance implications of its calling patterns.
|
|
la fonction refresh() d'un PagedResultsProvider est appelée à chaque fois que l'utilisateur effectue une action sur le paginateur et ce quelle que soit
l'action (last,next,previous,rewind) .
Ce qui fait que le paginateur effectue 2 actions(le refresh+l'action demandée par l'utilisateur).
voir la classe ResultsProvidersCacheBean et la methode private ResultsProviderFarm getProviderFarmFor(String name).
|
|
|
|
![]() |
|
_______________________________________________
ECM-tickets mailing list
[email protected]
http://lists.nuxeo.com/mailman/listinfo/ecm-tickets
