The idea itself is compelling enough. It is only fair to assume that the
implementation will get better over time. This also seems to be better than GWT
in security and (eliminating) DTO. I will post questions, if any on the
ICEFaces forum. Thanks Ted.
mani
View the original post :
Too good to be true!
How does ICEFaces know what changed without any support from the object graph ?
Does it manage the previous request's DOM to be able to indentify the changes ?
Does it render the object graph into DOM and then does the comparision ?
Is it a comparision by doing a full scan of
AJAX applications with rich client state needs only the incremental changes
that happened during the request (and not between save/commit). Otherwise we
will end up sending the entire (or relevant subset) object tree to the UI
everytime. This is inefficient and also requires the AJAX
If i understand correctly, the solution is to tie the source of the event and
potential areas of change using the reRender attribute. This should work for
most of the cases. This is true for GWT as well, since you could link the UI
event with the widget to be refreshed.
Probably i could have a
