Hi Mirko,
What do you mean with previous answer? There're two answers: true or
false. If you send 'A' twice and you will get true both times, the this
is no idempotent consumer pattern.
Best regards - Claus
Am Dienstag, den 21.06.2011, 14:19 +0200 schrieb Mirko Caserta
<[email protected]>:
Hello there,
a common requirement in my business is to provide a service with an
idempotent cache. That means that when a request that has already
been
processed gets into the service, instead of discarding the request
(as
currently implemented in the EIP component), the service should look
up in the cache and return the previous answer.
Because I'll need to reuse this thing in different projects, I was
wondering which would be the best choice for implementing this. I'm
willing to contribute patches of course if I get to implement this.
Thanks in advance.
Mirko
