RESTAGRA is a new medicine for the treatment of API dysfunction (AD). RESTAGRA can make your web services idempotent for up to 4 hours.
Take RESTAGRA about one hour before you plan to perform web services. Beginning in about 30 minutes and for up to 4 hours, RESTAGRA can help you become idempotent when someone accesses your endpoint. If you take RESTAGRA after a high-fat transaction (such as a WS-* transaction), the medicine may take a little longer to start working.
RESTAGRA is not for newborns, children, or women. Do not let anyone else take your RESTAGRA. RESTAGRA must be used only under a doctor’s supervision.
Like all medicines, RESTAGRA can cause some side effects. These effects are usually mild to moderate and usually don’t last longer than a few hours. Some of these side effects are more likely to occur with higher doses. The most common side effects of RESTAGRA are headache, flushing of the face, and blogorrhea. Less common side effects that may occur are temporary changes in reasoning (such as trouble telling the difference between GET and POST or quoting Roy Fielding for no particular reason), being more sensitive to criticism, or blurred worldview.
In rare instances, servers have reported idempotency that lasts many hours. You should call a doctor immediately if you ever experience idempotency for more than 4 hours. If not treated right away, permanent damage to your server could occur.
Denial of service attack, irregular network activity, and the Blue Screen of Death have been reported rarely in servers taking RESTAGRA. Most, but not all, of these servers had problems before taking this medicine, such as running Microsoft software. It is not possible to determine whether these events were directly related to RESTAGRA.
RESTAGRA may cause other side effects besides those listed here. If you want more information or develop any side effects or symptoms you are concerned about, discuss it at Sam’s place.
§
Where can I order RESTAGRA?
— Darryl ![]()
cheap-restagra-rx-from-canada.net, of course!
I need some of this, too. I have a serious API dysfunction problem right now!
Hahah, brilliant. Just brilliant.
Er… why would I want my web services to BE idempotent?
The reason to have a Web Service be idempotent is that if no response is returned for a request then you don’t know if it succeeded or failed – so you’d like to repeat the request. But if you don’t know if the results will be the same if you repeat the message, then you are hosed. Knowing that the type of request is meant to be idempotent means you can confidently re-send the request and know what the results should be.
It allows the system to be fault tolerant by allowing for messages to be re-tried. Most HTTP requests are idempotent (ex: head, get, put, delete).
Not that I have API dysfunction… My friend has API dysfunction and he’d like to have some of this medicine, but he’s too shy about it. Can I have some? Erm, for him, of course?
Cool!
I am no longer accepting public comments on this post, but you can use this form to contact me privately. (Your message will not be published.)
§
© 2001–9 Mark Pilgrim