How in practice do (or do they?) people use idempotentConsumer when creating "idempotent" web service interfaces?
Do they use idempotentConsumer only with one-way operations, do they have have idempotentConsumer + some kind of hand made reply message caching with request-response operations, or....? Because I can't see how idempotentConsumer can be used if you have request-response type of services, such as updateThisAndThatAndShowResults(). In case of response message getting lost, client would retry calling the idempotent service (which it can do as many times as it wants) but would not get the response message. -- View this message in context: http://camel.465427.n5.nabble.com/idempotentConsumer-is-not-idempotent-tp5733945p5733977.html Sent from the Camel - Users mailing list archive at Nabble.com.
