How are synchronization issues handled with any other AJAX RPC call back to application state?
Maybe I'm not following-- are you talking about the browser state or the serialized ViewState? Correct me if I'm wrong, but if the ViewState is serialized, then we have the luxury of clone by serialization, avoiding synchronization issues with the component tree instance(s) since each request would get a (transient) clone for processing. >>I do get what you mean by "selling" JSF and waiting for a round trip to >>the server for a full refresh. What if you were able to simply request >>a single component from the server to be re-rendered via AJAX? No >>waiting for a full refresh of the screen, no need to develop specialized >>intermediaries/RPC wrappers, just refresh this area or re-render the >>h:message for some component based on the state of your input. >>(ADF/Exadel/Avatar) > >How does this this handle synchronization issues? If I change the style and >the width of a text box (simple example), and tell the server to get give me >the new HTML, how is the client side (serialized, encoded and encrypted) state >syncronized? Any form submit between the AJAX/partial-render request and the >AJAX/partial render response is out of sync. > >Dennis Byrne > >
