camel-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "onder sezgin (JIRA)" <>
Subject [jira] [Commented] (CAMEL-10497) Improve documentation detailing websocket implementation details
Date Tue, 18 Apr 2017 07:44:41 GMT


onder sezgin commented on CAMEL-10497:

[~singram777]i got what you mean. however, i can not verify that i can see what you meant
in the code. if you could provide test env or steps that i can reproduce, i can provide better
documentation (i just don't want to add a simple statement to adoc and close the issue.) or
why don't you create github PR if you are already able to test and see the issue and maybe
you can do a blog post about your experience?

> Improve documentation detailing websocket implementation details
> ----------------------------------------------------------------
>                 Key: CAMEL-10497
>                 URL:
>             Project: Camel
>          Issue Type: Improvement
>          Components: camel-websocket, documentation
>    Affects Versions: 2.18.0
>            Reporter: Stuart Ingram
>            Assignee: onder sezgin
>            Priority: Minor
>             Fix For: Future
> Improve behavior documentation of this component, specifically around port workflows.
> While the initial port can be declaratively exposed for clients to connect the component
opens up two random(?) ports per client connected rather than communicate through the single
exposed port declared.
> This was not apparent from the documentation and makes this component somewhat inappropriate
for containerization which would be useful to consider when evaluating the 3 websocket implementations
currently available for Camel.

This message was sent by Atlassian JIRA

View raw message