[
https://issues.apache.org/jira/browse/CAMEL-14261?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16988763#comment-16988763
]
Claus Ibsen commented on CAMEL-14261:
-------------------------------------
Yeah I dont think it should send to itself. So lets fix it to send to all other
parties (we can update the doc to say that).
You are welcome to attempt to implement this.
> camel-websocket - Send to all but not to the sender
> ---------------------------------------------------
>
> Key: CAMEL-14261
> URL: https://issues.apache.org/jira/browse/CAMEL-14261
> Project: Camel
> Issue Type: Improvement
> Components: camel-websocket
> Affects Versions: 3.0.0
> Reporter: michael elbaz
> Priority: Trivial
>
> I want to propose improvement when sending to all if it possible to in some
> way (maybe adding specific parameter) avoid sending the message to the
> emitter itself because his sending the message so it just resource consumer
> and downgrade performance to send to him the message again maybe it can be
> useful in some case but in other it will be better to not sending again to
> him.
> By the way it will be nice to have some control over who is actually
> connected in order to be able to create some room concept and others... (just
> giving easy access to the connected users list should be enough)
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
