[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=14192341#comment-14192341 ] 

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

Commit 1635849 from [~arkurth] in branch 'vcl/trunk'
[ https://svn.apache.org/r1635849 ]

VCL-706
In vcl.sql, changed connectmethodport.protocol definition default value to TCP. Added connectmethodport.connectmethodid constraint.

Updated utils.pm::get_connect_method_info to retrieve connectmethodport information.

Changed all locations calling utils.pm::get_connect_method_info to $self->data->get_connect_methods for consistency.

Moved firewall_compare_update from Windows.pm, Linux.pm, and Ubuntu.pm to OS.pm since the code was duplicated.

Updated all locations which were using the protocol an port information to use the new multivalued connectmethodport information:
OS.pm::process_connect_methods
OS.pm::is_user_connected
OS.pm::get_connect_method_remote_ip_addresses
OS.pm::firewall_compare_update
Windows.pm::check_rdp_port_configuration

Other
Added additional registry keys to Windows.pm::clean_hard_drive. These allow the cleanup process to handle more items. Changed the cleanmgr.exe timeout from 120 seconds to 900. Newer versions seem to take a longer time.

Removed Linux.pm::sanitize_firewall. It was not called from anywhere and was not doing anything.

Cleaned up Ubuntu.pm's enable_firewall_port and disable_firewall_port.

> 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)