[
https://issues.apache.org/jira/browse/CAMEL-5828?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13665128#comment-13665128
]
Willem Jiang commented on CAMEL-5828:
-------------------------------------
Hi Riccardo,
Can you check out the latest camel code from
https://git-wip-us.apache.org/repos/asf/camel.git?
I made some changes when I applied your patch to fix some check style issues,
it could be easy for me to apply the patch if we are working on same repository.
DisruptorUnitOfWorkTest is use notify to check exchange onDone event, in seda
component, the exchange onDone event is sent after the
Synchronization.onComplete() is called, but it is different in camel-disruptor
component.
Willem
> Offer LMAX Disruptor pattern as an endpoint in CAMEL
> ----------------------------------------------------
>
> Key: CAMEL-5828
> URL: https://issues.apache.org/jira/browse/CAMEL-5828
> Project: Camel
> Issue Type: New Feature
> Reporter: Eric
> Assignee: Willem Jiang
> Fix For: Future
>
> Attachments: came-disruptor.incremental.patch, camel-disruptor.patch,
> README.md
>
>
> My system is an hybrid of CAMEL and LMAX Disruptor, where threads consuming
> from LMAX ringbuffer are feeding a "pool" of SEDA queues in a round-robin
> fashion. This system operates at very high-speed such as consumers from the
> SEDA queues and their producers are constantly blocking on the queues.
> Having a non-blocking, high-performance endpoint like LMAX Disruptor would be
> a great addition to CAMEL.
> LMAX Disruptor website: http://lmax-exchange.github.com/disruptor/
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira