You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@camel.apache.org by "Charles Moulliard (Assigned) (JIRA)" <ji...@apache.org> on 2012/01/06 09:28:39 UTC

[jira] [Assigned] (CAMEL-4498) camel websocket component

     [ https://issues.apache.org/jira/browse/CAMEL-4498?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Charles Moulliard reassigned CAMEL-4498:
----------------------------------------

    Assignee: Charles Moulliard
    
> 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
>            Assignee: Charles Moulliard
>              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