Typically in a web application, a user can save the data entered on a web page by clicking the SAVE/SUBMIT button whereby the data is saved to the database, while the user can remain to perform further edits on the page.
In terms of the standard request-response sequence with the web browser, does the response always automatically refresh the page (using latest data from the database) ?
Can this sequence be altered such that the page is not automatically reloaded, as a means to minimise traffic from the web server to browser ?
The preferred sequence of control is as follows :-
1) browser sends request to save data to the database via the web server (triggered by the user clicking SAVE/SUBMIT button.
2) while the database transation is in progress, the SAVE/SUBMIT button on the browser should be disabled (to prevent user inadventently initiating excessive database SAVE transactions), and preferreably the web server provides a work in progress indication (eg. hourglass or message) for the browser
3) when the database SAVE transaction has completed, the web server provides a response by removing the work in progress signal on the browser and re-enble the SAVE/SUBMIT button, but not reloading the entire page.
Will such a sequence minimise the traffic between browser & server ? We have remote users on low bandwidth accessing the web applications and we want ot xplore means to reduce data traffic to the browser.