title: Processing same concurrent request in REST
body: <p>Greetings SO community!
      I have a REST, jersey based, application. This application(due to nature of it's clients) receives same http requests (3-6 of them) at roughly the same time (~2-5s apart).
  Each request takes around 10s to process and brings back a ton of data (hitting DB, doing data massaging etc).
  In an ideal world I'd like to avoid having to process the same request multiple times and was thinking of coding some sort of request filter that would only allow unique requests go through, whist others would be blocked until such time when the allowed one returns. 
  Blocked requests would also then return the same data to the caller (by looking up cached response on the server)</p>
  
  <p>What are the pros/cons of this approach?
  Are there any better solutions to this other than changing client logic ;)</p>