[
https://issues.apache.org/jira/browse/CAMEL-4498?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13156535#comment-13156535
]
Lauri Lehmijoki commented on CAMEL-4498:
----------------------------------------
WebSocket allow synchronous communication from A to B, where B sits behind a
firewall.
This means that B (who sits behind a firewall) doesn't have to poll for new
messages from an endpoint. Neither does it have to send output data to a return
address defined by A. As a result, latency decreases and the integration model
becomes more simple. Another consequence of synchronous communication is that
the integration system can be stateless, removing the need for message queues
and aggregators in some cases.
> camel websocket component
> -------------------------
>
> Key: CAMEL-4498
> URL: https://issues.apache.org/jira/browse/CAMEL-4498
> Project: Camel
> Issue Type: New Feature
> Affects Versions: 2.9.0
> Reporter: Christopher Köster
> Labels: features
>
> We have build an implementation of websockets in Apache Camel. In combination
> with the strengths of Apache Camel you can push events from all given
> components (file, ftp, hazelcast, queue, etc.) to your browser. This offers
> great possibilities e.g. in process tracking, process driven forms and others.
> It is fully bidirectional (in contrast to the AHC-component) and can
> therefore be used for producers and consumers.
> To get a better idea of what has been done so far, please have a look at:
> https://github.com/catify/camel-websocket
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
