[
https://jira.jboss.org/jira/browse/RF-7906?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Francisco Jose Peredo Noguez updated RF-7906:
---------------------------------------------
Description:
When I do HTML/AJAX coding "by hand" (or using DWR or SeamWebRemoting) I can do
something I have found to be almost impossible to do with Richfaces: AJAX
Client Side Caching. Currently there is no way to cache a previous AJAX
rerender an re-play it again if the conditions for it to be re-played are met.
This would be a huge performance improvement because it would save the
application for going an fetching from the server information that has already
been fetched in previous rereder calls.
So I propose the creation of a a4j:rerenderCache component (and auxiliar
javascript functions) that make it easy to keep a client side cache of the
state of the UI.
Please look at the referenced forum thread for a proposal on how this component
could be used if implemented.
was:
When I do HTML/AJAX coding "by hand" (or using DWR or SeamWebRemoting) I can do
something I have found to me almost impossible to do with Richfaces: AJAX
Caching. Currently there is no way to cache a previous AJAX rerender an re-play
it again if the conditions for it to be re-played are met. This would be a huge
performance improvement because it would save the application for going an
fetching from the server information that has already been fetched in previous
rereder calls.
So I propose the creation of a a4j:rerenderCache component (and auxiliar
javascript functions) that make it easy to keep a client side cache of the
state of the UI.
Please look at the referenced forum thread for a proposal on how this component
could be used if implemented.
> a4j:rerenderCache to cache rerenders and reduce network and server use
> ----------------------------------------------------------------------
>
> Key: RF-7906
> URL: https://jira.jboss.org/jira/browse/RF-7906
> Project: RichFaces
> Issue Type: Feature Request
> Affects Versions: 3.3.1
> Reporter: Francisco Jose Peredo Noguez
>
> When I do HTML/AJAX coding "by hand" (or using DWR or SeamWebRemoting) I can
> do something I have found to be almost impossible to do with Richfaces: AJAX
> Client Side Caching. Currently there is no way to cache a previous AJAX
> rerender an re-play it again if the conditions for it to be re-played are
> met. This would be a huge performance improvement because it would save the
> application for going an fetching from the server information that has
> already been fetched in previous rereder calls.
> So I propose the creation of a a4j:rerenderCache component (and auxiliar
> javascript functions) that make it easy to keep a client side cache of the
> state of the UI.
> Please look at the referenced forum thread for a proposal on how this
> component could be used if implemented.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
_______________________________________________
richfaces-issues mailing list
[email protected]
https://lists.jboss.org/mailman/listinfo/richfaces-issues
