camel-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Ioannis Polyzos (JIRA)" <>
Subject [jira] [Commented] (CAMEL-3983) Added Support for Serialization and Message Headers to Hazelcast SEDA functionality
Date Wed, 01 Jun 2011 19:56:47 GMT


Ioannis Polyzos commented on CAMEL-3983:

 The queue consumers register hazelcast listeners and are get notified upon events on the
queue, such as addition of an item. In the scenario that we have 5 consumers listening on
a queue with the use of a listener, upon addition of a new item all of them will be notified
and react upon the very same event while the data will remain on the queue.

 On the other hand SEDA component implements a work queue and focus on distributing of tasks
to different consumers. Unlike the case of queue consumers that make use of listeners, SEDA
make use of the poll() method on the queue which means that will remove and return the head
of the queue. Every item on the queue will retrieved by only one consumer and then it will
be deleted.

 It works in the same way as the plain SEDA component but by using the hazelcast underneath,
distribution can scale not only cross threads but it can scale cross different machines....

> Added Support for Serialization and Message Headers to Hazelcast SEDA functionality
> -----------------------------------------------------------------------------------
>                 Key: CAMEL-3983
>                 URL:
>             Project: Camel
>          Issue Type: New Feature
>          Components: camel-hazelcast
>    Affects Versions: 2.8.0
>            Reporter: Claus Straube
>             Fix For: Future
>         Attachments: SEDA-CAMEL-3983-2.patch, SEDA-CAMEL-3983.patch, hazelcast_seda_headers_04.diff,
hazelcast_seda_serialization_and_headers_01.diff, hazelcast_seda_serialization_and_headers_02.diff,
> The current implementation looses headers that are given to a 'hazelcast:seda:foo' route
and is has problems serializing complex objects inside body that are not serializable. 

This message is automatically generated by JIRA.
For more information on JIRA, see:

View raw message