heroku - Jersey and AsyncResponse vs. Redirects -

currently using jersey 1.0 , switch 2.0. rest requests may last on second or 2 use following pattern:

1. client calls or put
2. server returns polling url client
3. the client polls url until gets redirect completed resource

pretty standard , straightforward. however, noticed jersey 2.0 has asyncresponse capability. looks done no changes on wire. in other words, client still blocks result while server asynchronously processing request.

so this? should using instead of current asynchronous approach calls >1 second? or keep connections freed on server calls few hundred milliseconds?

i want server scalable possible approach use can tedious client. asyncresponse seems super simple i'm not sure how work heroku service want short connection times.

asyncresponse presumably gives more scalability within web app server standard standard requests in terms of thread pooling resources, don't think changes client experience continue block on read on connection. therefore, if implemented polling solution client side, won't add of value imho.