ok here is my scenario - using model, vew , controller architecture:
-- user submits the view page to the controller
-- controller issues a server.execute on a model page to update the changed
information
-- upon successful updating of the the information, the controller issues a
server.transfer back to the view
-- everything is fine at at this point, however, if the user hits the
'refresh' button on his/her browser (for whatever reason) the
page gets resubmitted. now - the original items are still in the
request object from the first time around because the page never went out of
scope - so this causes another update to be inssued because changes are
detected between what is in the database and what is in the request.form
collection.
hope this is a bit clearer - by the way, im open to any suggestions about
architecture alternatives, etc.
thanks much for the help.
jt
"Roland Hall" <nobody@nowhere > wrote in message
news:ej******** ******@TK2MSFTN GP09.phx.gbl...
"JT" wrote in message news:eo******** *******@tk2msft ngp13.phx.gbl.. .
: is there a way to clear out the request.form collection, or the entire
: request object, for that matter??
:
: im using server.transfer and this can be troublesome in cases where you
need
: the request.form items to be reset.
Please explain why it makes a difference what is in the page header.
Perhaps there is a different approach to accomplish the goal you have
set?!
--
Roland Hall
/* This information is distributed in the hope that it will be useful, but
without any warranty; without even the implied warranty of merchantability
or fitness for a particular purpose. */
Technet Script Center - http://www.microsoft.com/technet/scriptcenter/
WSH 5.6 Documentation -
http://msdn.microsoft.com/downloads/list/webdev.asp MSDN Library - http://msdn.microsoft.com/library/default.asp
