[jira] [Commented] (VCL-706) Allow a Connect Method to Specify a Port Range or Port List

["ASF subversion and git services (JIRA)" <ji...@apache.org>]

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

ASF subversion and git services commented on VCL-706:
-----------------------------------------------------

Commit 1639027 from [~jfthomps] in branch 'vcl/trunk'
[ https://svn.apache.org/r1639027 ]

VCL-174 - NAT - support for sites that have small IP address ranges
VCL-706 - Allow a Connect Method to Specify a Port Range or Port List
VCL-655 - Manage groups - create a default or none user group

vcl.sql:
-modified natlog: changed types of fields to make more sense and to match any referenced fields
-added inserts for connectmethodport table
-added 'Default for Editable by' user group to inserts for usergroup table
-added 'Default for Editable by' to groups admin user is member of
-added constraints for nathost, natlog, natmap, and natport

> 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 was sent by Atlassian JIRA
(v6.3.4#6332)