Mailing-List: contact commits-help@guacamole.incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@guacamole.incubator.apache.org
Date: Thu, 9 Jun 2016 21:09:21 +0000 (UTC)
From: "Michael Jumper (JIRA)" <jira@apache.org>
To: commits@guacamole.incubator.apache.org
Message-ID: <JIRA.12977390.1465506541000.45057.1465506561262@Atlassian.JIRA>
In-Reply-To: <JIRA.12977390.1465506541000@Atlassian.JIRA>
References: <JIRA.12977390.1465506541000@Atlassian.JIRA> <JIRA.12977390.1465506541176@arcas>
Subject: [jira] [Created] (GUACAMOLE-49) Handle printing synchronously
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
archived-at: Thu, 09 Jun 2016 21:09:26 -0000

Michael Jumper created GUACAMOLE-49:
---------------------------------------

             Summary: Handle printing synchronously
                 Key: GUACAMOLE-49
                 URL: https://issues.apache.org/jira/browse/GUACAMOLE-49
             Project: Guacamole
          Issue Type: Sub-task
          Components: RDP
            Reporter: Michael Jumper
            Assignee: Michael Jumper


As mentioned in GUACAMOLE-44:

{quote}
Download via SFTP or RDPDR is working perfectly with the new changes. Printing, however, is not. The RDP printing code begins streaming immediately, not waiting for an "ack" from the client.

This means the GET request to the stream endpoint will likely occur *after* data has already been sent, resulting in data being dropped. If the GET request occurs after the stream has closed, then it will block until some other stream with that index is opened, leading to mismatches in the downloaded results.
{quote}

The print process within the RDP connection needs to be modified to wait for the initial "ack", or blobs may end up being dropped.


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