You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@guacamole.apache.org by "Michael Jumper (JIRA)" <ji...@apache.org> on 2016/05/19 06:09:13 UTC

[jira] [Created] (GUACAMOLE-26) Add support for overall concurrency limits

Michael Jumper created GUACAMOLE-26:
---------------------------------------

             Summary: Add support for overall concurrency limits
                 Key: GUACAMOLE-26
                 URL: https://issues.apache.org/jira/browse/GUACAMOLE-26
             Project: Guacamole
          Issue Type: Improvement
          Components: guacamole-auth-jdbc, Documentation, guacamole-auth-jdbc-mysql, guacamole-auth-jdbc-postgresql, guacamole-docker
            Reporter: Michael Jumper
            Priority: Blocker
             Fix For: 0.9.10-incubating


{panel:bgColor=#FFFFEE}
*The description of this issue was copied from [GUAC-1512|https://glyptodon.org/jira/browse/GUAC-1512], an issue in the JIRA instance used by the Guacamole project prior to its acceptance into the Apache Incubator.*

Comments, attachments, related issues, and history from prior to acceptance *have not been copied* and can be found instead at the original issue.
{panel}

Guacamole currently supports concurrency limits at a per-connection level and a per-user level, but not overall. If the absolute total number of connections to a Guacamole server must be limited to a specific amount, this is impossible in the current system. This is particularly important if the licensing of some proprietary remote desktop server prohibits greater than a certain number of connections, but there are multiple Guacamole connections pointing to this server.

An additional property, like "mysql-max-connections" and "postgresql-max-connections", would satisfy this need.



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