Hey Claus, Thanks for your reply.
SQS doesn't guarantee FIFO, so consumers already have to handle things being out-of-order: http://aws.amazon.com/sqs/faqs/#Does_Amazon_SQS_provide_first_in_first_out_FIFO_access_to_messages Based on GenericFileConsumer, perhaps this is a better patch: https://gist.github.com/2139866 I'm using akka-camel to consume the messages, so async support shouldn't be a problem. =) Given the lack of FIFO in SQS, do you think my patch is appropriate to submit for inclusion in a future release? Thanks, - Dan -- View this message in context: http://camel.465427.n5.nabble.com/Better-Way-to-Achieve-Parallel-Processing-of-SQS-Messages-tp5578135p5580926.html Sent from the Camel - Users mailing list archive at Nabble.com.
