guacamole-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF GitHub Bot (JIRA)" <>
Subject [jira] [Commented] (GUACAMOLE-5) Allow creation of per-connection share links
Date Sat, 16 Jul 2016 08:20:20 GMT


ASF GitHub Bot commented on GUACAMOLE-5:

GitHub user mike-jumper opened a pull request:

    GUACAMOLE-5: Move common equals() / hashCode() of Identifiable implementations to base

    To make developers lives easier, including my own, this change moves the common `equals()`
and `hashCode()` of the `Identifiable` implementations used throughout the Guacamole API to
a common base class: `AbstractIdentifiable`.
    The logic is identical to all past version of Guacamole. The code in question is simply
no longer duplicated.

You can merge this pull request into a Git repository by running:

    $ git pull abstract-identifiable

Alternatively you can review and apply these changes as the patch at:

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #29
commit 31887264c5a7111d08b27c0651089daaae139dc4
Author: Michael Jumper <>
Date:   2016-07-16T08:14:09Z

    GUACAMOLE-5: Move common identifier equals() / hashCode() of abstract Identifiable implementations
to common base class.


> Allow creation of per-connection share links
> --------------------------------------------
>                 Key: GUACAMOLE-5
>                 URL:
>             Project: Guacamole
>          Issue Type: New Feature
>            Reporter: Michael Jumper
>            Assignee: Michael Jumper
>             Fix For: 0.9.10-incubating
> {panel:bgColor=#FFFFEE}
> *The description of this issue was copied from [GUAC-1074|],
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}
> Depending on connection and user permissions, users should be able to create one-time
share links that allow external or internal users to share active connections.
> Considering that these links may be needed by groups of users, each link should have
the option to be:
> # One-time use
> # Multi-use (lasts until the sharing user disconnects)
> Once a user joins a connection, their presence should be exposed in the interface, and
the owning user should be able to grant/revoke permission to use the keyboard/mouse, kick
individual users, etc.

This message was sent by Atlassian JIRA

View raw message