[
https://issues.apache.org/jira/browse/CAMEL-3590?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12986829#action_12986829
]
Ioannis Polyzos commented on CAMEL-3590:
----------------------------------------
Hi Richard,
Thank you very much for the feedback it is very appreciated.
I have gone through the changes you suggested (very good points) and a new
patch is attached. In the new patch the pool interval is configurable through
the "poolInterval" parameter and the consumer make use of the
ExecutorServiceStrategy.
Regarding the name, indeed, I have chosen this name because the component
uses only a subset of the Hazelcast data structures. To be more specific it
uses only the BlockingQueue implementation. Though I wouldn't mind at all to
rename the project if you believe that another name would be more apropriate.
> New component: camel-hzlq
> -------------------------
>
> Key: CAMEL-3590
> URL: https://issues.apache.org/jira/browse/CAMEL-3590
> Project: Camel
> Issue Type: New Feature
> Affects Versions: 2.7.0
> Reporter: Ioannis Polyzos
> Priority: Minor
> Attachments: camel-hzlq-20110126.patch, camel-hzlq-20110126.tar.gz
>
>
> I am submitting this component for your review and consideration for its
> addition as an official Camel component...
> HzlQ component implements a work-queue on top of the Hazelcast in-memory
> data-grid. Its purpose is to support asynchronous SEDA architectures, similar
> to the core "SEDA" component. By making use of Hazelcast's implementation of
> BlockingQueue, it allows the system to scale across multiple machines with
> minimal or no configuration while the replication features provided increase
> reliability and fault-tolerance.
> For more information on Hazelcast please refer to : http://www.hazelcast.com/.
> (Hazelcast is released under Apache 2.0 License)
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
