Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    text
    copied!<p>Restful spesification is still at early ages of its life. But this problem should be considered as 2 part. Client and Server.</p> <p>Client:</p> <p>For the client side recent changes at last year became mature enough. And recently a non blocking client from based on <a href="https://github.com/sonatype/async-http-client" rel="nofollow">Jeanfrancois Arcand</a> was implemented and pushed to repository. There is an explanation <a href="http://blogs.oracle.com/PavelBucek/entry/jersey_non_blocking_client" rel="nofollow">here</a>.</p> <p>Server:</p> <p>For the server side, it is still immature. The adoption of the new servlet specification is quite slow and as a developer I am expecting <a href="http://jcp.org/en/jsr/detail?id=339" rel="nofollow">JSR 339</a> to address these issues as well. And this is also addressed at the JSR spec clearly with these sentences.</p> <blockquote> <p>JAX-RS 1.1 defines a synchronous request response model on the server side. This JSR will specify a simple asynchronous request processing model such that a response can be returned asynchronous to the request. Servlet 3.0 can be leveraged to enable such support but implementations may choose to use other container-specific APIs instead.</p> </blockquote> <p>However there are other alternatives too. Projects such as Jetty are addressing such kind of problems elegant as in this <a href="http://java.dzone.com/news/asynchronous-restful-web-appli" rel="nofollow">example</a>. I can only suggest you to consider other alternatives as the community is growing.</p>
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload