the browser works with a async request/response model.
say the user naivates to your page, enters data then clicks a button. here
is what happens.
1) the user type urls
- browser send get request and wiats for response
- the asp code run and builds an html page and send to browser.
- the browser render the page
2) the user fills in data and clicks button
- the browser posts the from data to the server and waits for response
- the asp code runs, processes the click , validates and build a new html
page and send to browser
- the browser render the new page.
if a user types data between the click (postback) and before the render,
then they are lost becuase they updated the old page which is replaced by
the new page.
-- bruce (sqlwork.com)
"gsalbertson" <gs*********@albertsons.comwrote in message
news:e9**************@TK2MSFTNGP04.phx.gbl...
am new to asp.net and have a question on just what is processing on the
server and what is processing on the client. I have an asp.net page with
html controls on it, say a couple of text boxes and a button. The user
enters a number in one textbox, then the code behind does stuff -- let's
say it validates the number, adds the number to 100, then displays the new
number in the 2nd textbox. Once the user hits the button, isn't the
validation and calculation processing being done on the server, or is that
the client? Because if the server is really really really slow, and it is
still processing calcuations, the client isn't prevented from doing other
keystores, correct?
thanks.
