Hyprint run in the RDP server : Once we print the document through HyPrint
it only converts the document in PDF and saves in the Shared drive.
*That's the only thing it does and sends the file name through the static
channel.*
Now once we get the file name we form the url and use the guacamole code as
follows : After that guacamole handles everything.
{code:none}
ManagedFilesystem.downloadFile(managedClient,managedClient.filesystems[0]
,"/"+filename,false);
{code}
On Thu, Mar 15, 2018 at 2:03 PM, Amarjeet Singh <[email protected]>
wrote:
> If this hyprint uses a static channel, why not use Guacamole's existing
>>
>> support for static channels?
>>
>> I have used Guacamole's existing support for static channels?
>
>
>
> On Thu, Mar 15, 2018 at 1:53 PM, Mike Jumper <[email protected]>
> wrote:
>
>> On Thu, Mar 15, 2018 at 1:16 AM, Amarjeet Singh <[email protected]>
>> wrote:
>>
>> > ...
>> >
>> > I want to remove the dependency here as our hyprint static channel saves
>> > the file in the Shared drive and If I pass the below URL and download is
>> > disabled using the above flag. It calls the get handler where I have
>> > disabled the downloads.
>> >
>>
>> If this hyprint uses a static channel, why not use Guacamole's existing
>> support for static channels?
>>
>> If you're set on having an application running within the remote desktop
>> that deals with the printing on that side, why not pass that printout
>> using
>> the normal RDPDR print mechanisms?
>>
>> It sounds like the issue here is not that you need to change the Guacamole
>> protocol (which, again, is something you should only consider with extreme
>> skepticism), but that you need to work out a usable transport that does
>> not
>> rely on a hack powered by drive redirection and Guacamole's special
>> "Download" folder.
>>
>> - Mike
>>
>
>
