[KNOWLEDGE NEEDED] I want to know in what AutoSubmit is asynchronous

Question

Hi.
I'm asking a kind of question that is to me a reel enigma.
To my definition, asynchronous is invisible to the end-user using his internet browser. But when an input component has autoSubmit set to true, after navigating out of it, the page is submitted, to prove it the pointer like change to the wait one. I'm confused with something called cross site scripting ?
The main point to prove autoSubmit isn't asynchonous and refresh the entire page, like any classic html form submit, put you on a SLOW computer. Have two input component with boths autoSubmit. F. ex. two input text. The test case is :
- enter a value in the first
- hit tab to go the second input -> PPR, autosubmit is triggered
- quickly, enter a value in the second input and hit tab another time
- PPR, autosubmit triggered by the first component ends -> the changed value in the second input is reset to the initial value
So if you've been following me, it's nothing asynchronous but more synchronous. Right ?
Please, I really need help on this one. I bet my shirt it's clear for a lot of people, so take a minute to make me level up :D
Greatings will be awarded to the one that make me understand.
Sincerily.
Fred.
nota : I've been reading this just before writing this post : http://www.oracle.com/technology/pub/articles/jellema-muir-adf.html.

Answer 1

Oh yes, of course.
This is interesting. I was confused because I mostly use autoSubmit combined with PPR on input element, but in the context of an editable af:table, with around 10 lines, 10 columns, inputTexts and selectOneChoice. In my case, selects are dependant over input, so I autoSubmit the inputs, and PPR the selects on these inputs ; but the whole table is refreshed, since in ADF, rows aren't not stamped.
It's a real usuability issue to me and m users.
Thanks anyway. You'll get what I promised :
*** Hora to Todd Bao for this clear answer !!! **** Bravo ***
Regards
Fred