This week's book giveaway is in the OO, Patterns, UML and Refactoring forum. We're giving away four copies of Refactoring for Software Design Smells: Managing Technical Debt and have Girish Suryanarayana, Ganesh Samarthyam & Tushar Sharma on-line! See this thread for details.
Can anybody tell me from exam point of view that which of the following methods are IDEMPOTENT or not ?
GET : IDEMPOTENT or not POST : IDEMPOTENT or not PUT : IDEMPOTENT or not HEAD : IDEMPOTENT or not DELETE : IDEMPOTENT or not TRACE : IDEMPOTENT or not OPTIONS : IDEMPOTENT or not CONNECT : IDEMPOTENT or not
idempotent means that the same resulting state change is made regardless of whether a method is execute 1 time or 100 times. An idempotent method is one that can be repeated with no negative side effects.
BEA 8.1 Certified Administrator, IBM Certified Solution Developer For XML 1.1 and Related Technologies, SCJP, SCWCD, SCBCD, SCDJWS, SCJD, SCEA,
Oracle Certified Master Java EE 5 Enterprise Architect
i have also been pondering over this "Idempotent" stuff from some time. Read some where in previous posts that according to JSP specs, Put and Delete also may have some side effects on repetative execution. So, they are non-idempotent.
It is confusing.Request somebody to clear the mud....
To know recursion, you must first know recursion...
Joined: Feb 10, 2004
i came across this....
Methods may also have the property of "idempotence" in that (aside from error or expiration issues) the side-effects of N > 0 identical requests is the same as for a single request. The methods GET, HEAD, PUT and DELETE share this property.