[
https://issues.apache.org/jira/browse/VCL-706?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nathaniel Sherry updated VCL-706:
---------------------------------
Description:
Currently, when configuring a connect method, only one port can be listed. It
would be nice if a list of ports could be provided, instead.
For a connect method like VNC, one way to support different resolutions is to
run several VNC servers on adjacent ports.
Allowing noVNC to connect to a VNC server which does not support web sockets
requires running a service like websockify, which needs to operate on a
separate port to allow normal VNC connections to continue to work.
was:
Currently, when configuring a connect method, only one port can be listed. It
would be nice if a list of ports could be provided, instead.
For a connect method like VNC, one way to support different resolutions is to
run several VCL servers on adjacent ports.
Allowing noVNC to connect to a VNC server which does not support web sockets
requires running a service like websockify, which needs to operate on a
separate port to allow normal VNC connections to continue to work.
> Allow a Connect Method to Specify a Port Range or Port List
> -----------------------------------------------------------
>
> Key: VCL-706
> URL: https://issues.apache.org/jira/browse/VCL-706
> Project: VCL
> Issue Type: Improvement
> Components: database
> Affects Versions: 2.3
> Reporter: Nathaniel Sherry
> Priority: Minor
>
> Currently, when configuring a connect method, only one port can be listed. It
> would be nice if a list of ports could be provided, instead.
> For a connect method like VNC, one way to support different resolutions is to
> run several VNC servers on adjacent ports.
> Allowing noVNC to connect to a VNC server which does not support web sockets
> requires running a service like websockify, which needs to operate on a
> separate port to allow normal VNC connections to continue to work.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
