camel-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Richard Kettelerij (JIRA)" <>
Subject [jira] Commented: (CAMEL-3590) New component: camel-hzlq
Date Wed, 26 Jan 2011 00:16:44 GMT


Richard Kettelerij commented on CAMEL-3590:

Thanks for contributing. I took the liberty to review your patch, a few minor comments/questions:

- Is there a reason to name the component "camel-hzlq" instead of just "camel-hazelcast"?
Is it because the component supports a subset of Hazelcast its data structures?
- Is it possible to make the polling interval of the consumer configurable? It's currently
set to 1 second, which seems reasonable but might not work for everyone.
- Consider using {{ExecutorServiceStrategy}} in the consumer instead of directly using Java
thread pools. You can look up an implementation from the {{CamelContext}}.

> New component: camel-hzlq
> -------------------------
>                 Key: CAMEL-3590
>                 URL:
>             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 :
> (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.

View raw message