Home/ Questions/Q 4265334
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-05-21T06:36:36+00:00

I’ve read about asynchronous HTTP and REST and how can you return a resource

  • 0

I’ve read about asynchronous HTTP and REST and how can you return a resource after POST-ing to initiate a long running task and then polling that resource to get the task’s status.
I wonder what happens if I have two machines that are load-balanced and one will receive the initial POST and the other a subsequent GET. The second will not be aware of what the first one started, unless I use a common storage to keep the task’s state.
How can I prevent that if I want to keep the state only on the client?

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    When you did the POST to initiate the long running task, you really should return a URI in the location header to point to the running task. e.g.

    POST /LongTasks
=>
201 Created
Location: /RunningTask/233


GET /RunningTask/233
=> 
Content-Type: text/plain

InProgress

    At that point, you have a URL to the resource that represents the running task. At that point the load balancing issue is the same as any other. You cannot create state on the server that is accessible by the client that does not have a URI.

    However, as long as those two loadbalancing servers are directly accessible you could do 

    POST http://example.org/LongTasks
=>
201 Created
Location: http://serverA.example.org/RunningTask/233


GET http://serverA.example.org/RunningTask/233
=> 
Content-Type: text/plain

InProgress
    • 0