Return to Question

The product is optional since it depends on the nature of the process (e.g. a video encoding process has a product while a machine shutdown process does not).

Again the product is optional since it depends on the nature of the process.

The product is optional since it depends on the nature of the process (e.g. a video encoding process has a product while a machine shutdown process does not) and only makes sense for the POST method.

Again the product is optional since it depends on the nature of the process and only makes sense for the POST method.

Here is the pattern that I thought about for accepting a single asynchronous HTTP request at a time (i.e. a request which has not yet been fulfilled when the response is sent):

And here is the pattern that I thought about for accepting multiple asynchronous HTTP requests at a time:

So it seems to me that asynchronous HTTP requests cannot be idempotent with the pattern accepting multiple asynchronous HTTP requests at a time, since part of their intended effect is to always create resources on the server (e.g. /process/123 and /product/123). However it seems to me that asynchronous HTTP requests can be idempotent with the pattern accepting a single asynchronous HTTP request at a time, depending on their intended effect, since they do not have this systematic resource creation as part of their intended effect.

Here is the pattern that I thought about for a resource accepting a single asynchronous HTTP request at a time (i.e. a request which has not yet been fulfilled when the response is sent):

And here is the pattern that I thought about for a resource accepting multiple asynchronous HTTP requests at a time:

So it seems to me that asynchronous HTTP requests cannot be idempotent with the multiple asynchronous HTTP requests pattern, since part of their intended effect is to always create resources on the server (e.g. /process/123 and /product/123). However it seems to me that asynchronous HTTP requests can be idempotent with the single asynchronous HTTP request pattern, depending on their intended effect, since they do not have this systematic resource creation as part of their intended effect.