[
https://issues.apache.org/jira/browse/CAMEL-4498?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13173207#comment-13173207
]
Claus Straube commented on CAMEL-4498:
--------------------------------------
Hi Claus,
yes I've seen that on the dev list...
Ok. So we're trying to get into 2.9.1. We've got enough man power to provide
what you need and I think we've a good state at all (except the OSGi stuff).
But we need some quicker attention / feedback from the core team. Chris opened
the issue end of Sept. (incl. code) and the first reaction was nearly two
months later. That's a long time... I know you're all busy people, but we want
to provide a high quality component and for that we need a little bit of your
time ;)
Best regards - Claus
> 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
> Fix For: 2.9.1, 2.10
>
>
> 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
