You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@camel.apache.org by "Emilien (JIRA)" <ji...@apache.org> on 2015/06/16 10:06:00 UTC

[jira] [Comment Edited] (CAMEL-8861) Add a factory to support custom websocket sub-protocol

    [ https://issues.apache.org/jira/browse/CAMEL-8861?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14587636#comment-14587636 ] 

Emilien edited comment on CAMEL-8861 at 6/16/15 8:05 AM:
---------------------------------------------------------

Exaclty, myProtocol is the sub protocol. In the provided patch, if no configuration is defined, then the default websocket factory is added to the factory map. This approach also allows users to override the default websocket factory. But you are right, adding the defaultSocketFactory to the map if not present in the conf should also helps to simplify it.



was (Author: ebondu):
Exaclty, myProtocol is the sub protocol. In the provided patch, if no configuration is defined, then the default websocket factory is added to the factory map. This approach also allows users to override the default websocket factory. But you are right, adding the defaultSocketFactory to the map if not present in the conf should also helps to simplify the conf.


> Add a factory to support custom websocket sub-protocol
> ------------------------------------------------------
>
>                 Key: CAMEL-8861
>                 URL: https://issues.apache.org/jira/browse/CAMEL-8861
>             Project: Camel
>          Issue Type: New Feature
>          Components: camel-websocket
>            Reporter: Emilien
>             Fix For: 2.16.0
>
>         Attachments: camel.patch
>
>
> Websocket supports sub-protocol definition (see https://tools.ietf.org/html/rfc6455#section-1.9). However, there is no way to provide your own websocket implementation to handle your own subprotocol. Adding a configurable websocket factory to the component could enable this functionnality.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)