[
https://issues.apache.org/jira/browse/CAMEL-9393?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claus Ibsen resolved CAMEL-9393.
--------------------------------
Resolution: Fixed
Assignee: Claus Ibsen
> Add ability to send a message to multiple defined connections with guaranty
> of delivery
> ---------------------------------------------------------------------------------------
>
> Key: CAMEL-9393
> URL: https://issues.apache.org/jira/browse/CAMEL-9393
> Project: Camel
> Issue Type: New Feature
> Components: camel-atmosphere-websocket
> Reporter: Pavlo Kletsko
> Assignee: Claus Ibsen
> Labels: patch
> Fix For: 2.17.0
>
> Original Estimate: 24h
> Remaining Estimate: 24h
>
> For that moment of time there are two ways of sending message (to all
> available connections and to one specific) I want to extend this by providing
> a list of connection keys for broadcasting a message. Addition to this I want
> to be notified about that one or more connections were not available and have
> not received the message. So I can handle this situation somehow for example
> store the message or re send.
> To solve this
> 1) I create a new constant CONNECTION_KEY_LIST =
> "websocket.connectionKey.list"
> for transferring connections which should receive the message and ERROR_TYPE
> = "websocket.errorType"
> MESSAGE_NOT_SENT_ERROR_TYPE = 1
> to mark the callback event when some connections have not received the
> message.
> 2) create sendNotDeliveredMessage method in WebsocketConsumer for re sending
> the error event.
> 3) change WebsocketEndpoint to provide access to WebsocketConsumer
> 4) change WebsocketProducer to handle a new case (broadcast to defined list
> of connections and send error event in case some connections have not
> received the message)
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
