idempotent in ASP.NET 2.0

  • Thread starter Thread starter Stefano
  • Start date Start date
S

Stefano

Hi all,

what about "idempotent" problem in ASP.NET 2.0 ?
Will there some help for developers from the ASP.NET framework about it?

Thank you

Bye
 
Not familiar with English but I'm afraid I don't give this the same meaning.
Could you elaborate a bit more on this problem (I've seen this for header
files but I don't see how it relates to ASP.NET) ?
 
Oh... excuse me.

OK, I mean... HTTP Request Idempotent... when the same request is sent to
the server, for example when the user press F5 on IE, and redo the postback.

Bye
 
Humm... this is "by design". The goal of the F5 key is precisely to send the
exact same request to the server. In some cases , it's likely what the
developer/user wants ?!

IMO your best bet is to create another thread to explain what exact problem
it causes in your application and someone will hopefully suggest how to
handle this in your particular case...

Patrice

--
 
Patrice, my question is in general.

The HTTP Request Idempotent is a common problem in web applications.

I know what it is, and I'm not finding an explanation about Idempotent, and
the function of the F5 button.

I would like to know if in ASP.NET 2.0, we will have tools to manage
idempotent issues.

Thank you anyway.

Bye
 
AFAIK no and I think it's not possible to come up with a general solution
for this...

Is this a real problem ? In most cases I can think it :
- delete a record that doesn't exist any more (no big deal)
- update a record that was previosuly containing other values (but it looks
to me what is expected)
- insert again a new record (but it looks also to me what is expected)

Could you explain a scenario in which it causes a problem so that we can
start from there ?

Patrice

--
 
Patrice,

I believe, you cannot give me the answer I'm looking for: "idempotent and
ASP.NET 2.0"

I have no time to discuss in wide way.
So, thank you very much anyway.... and excuse me.

Bye
 
Stefano,

Did you just discover this word, or what? There IS no "HTTP Request
Idempotent... problem." You might just as well ask if ASP.Net solves the
"POST method problem."

An HTTP Request is deemed Idempotent if the result of the Request will be
the same when the Request is repeated. It's just a term used to define a
behavior. End of story. If you request a page, and then press F5 to refresh
it, you have sent an Idempotent Request. Why would this be a "problem?"

I feel like I'm reading "The Emporer's New Clothes" here!

--
HTH,
Kevin Spencer
..Net Developer
Microsoft MVP
I get paid good money to
solve puzzles for a living
 
I don't see where the problem is.

You need to design your software to be able to handle this, not rely on the
framework to do so... To predict situations where this would be a problem
would be impossible.

i.e. think about ebay and the number of times you hit F5 there trying to
win a bid vs someone entering a contest 1000 times...

Again.. what *problem*

humans?
 
yes, I know... I have to manage idempotent, and I'm doing this, in every web
application I made.

But, my simple question was: "does ASP.NET 2.0 introduce helps to manage
idempotent requests?"

I don't understand why you want learn me about idempotent request and how to
manage it, instead.

My english is so bad... I know. Maybe for this reason you cannot understand
what I want mean.

Thank you so much.

Bye
 
yes, I know... I have to manage idempotent, and I'm doing this, in every web
application I made.

But, my simple question was: "does ASP.NET 2.0 introduce helps to manage
idempotent requests?"

I don't understand why you want learn me about idempotent request and how to
manage it, instead.

My english is so bad... I know. Maybe for this reason you cannot understand
what I want mean.

Thank you so much.

Bye
 
Nothing I've seen will help you manage these requests. It still relys on
just Page.IsPostBack.
 
As a side note you'll have in ASP.NET 2.0 a mechanism that allows to call
server side code without refreshing the page...
As you know what is your problem, you'll likely know if it could solve it.

Patrice
--
 
Back
Top