Re: [FreeRDP-devel] clipboard filetransfers

2019-02-19 Thread Alexandr via FreeRDP-devel
-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 В Вт, 19/02/2019 в 17:55 +0300, Alexandr via FreeRDP-devel пишет: > В Вт, 19/02/2019 в 15:18 +0100, Armin Novak via FreeRDP-devel пишет: > > The spec [MS-RDPECLIP] tells that streamID is arbitrary in the > > request > > and the reponse to a request m

Re: [FreeRDP-devel] clipboard filetransfers

2019-02-19 Thread Alexandr via FreeRDP-devel
-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 В Вт, 19/02/2019 в 15:18 +0100, Armin Novak via FreeRDP-devel пишет: > The spec [MS-RDPECLIP] tells that streamID is arbitrary in the > request > and the reponse to a request must match. > exactly. but does libfreerdp provide any way to deserialize

Re: [FreeRDP-devel] clipboard filetransfers

2019-02-19 Thread Armin Novak via FreeRDP-devel
The spec [MS-RDPECLIP] tells that streamID is arbitrary in the request and the reponse to a request must match. On 2/19/19 2:22 PM, Alexandr via FreeRDP-devel wrote: > В Вт, 19/02/2019 в 13:05 +0100, Armin Novak via FreeRDP-devel пишет: >> Ok, but for some unix like system? > >> the server -> cli

Re: [FreeRDP-devel] clipboard filetransfers

2019-02-19 Thread Alexandr via FreeRDP-devel
-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 В Вт, 19/02/2019 в 13:05 +0100, Armin Novak via FreeRDP-devel пишет: > Ok, but for some unix like system? > > the server -> client system looks like this (just like the other way > around) > > -> Announce a format FileGroupDescriptorW with a list o

Re: [FreeRDP-devel] clipboard filetransfers

2019-02-19 Thread Armin Novak via FreeRDP-devel
Ok, but for some unix like system? the server -> client system looks like this (just like the other way around) -> Announce a format FileGroupDescriptorW with a list of available files (relative paths) from server   -> That is announced in ServerFormatList   -> That contains the file FILEDESCRI

Re: [FreeRDP-devel] clipboard filetransfers

2019-02-19 Thread Alexandr via FreeRDP-devel
-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 В Вт, 19/02/2019 в 11:21 +0100, Armin Novak via FreeRDP-devel пишет: > Hi, > > > xfreerdp already supports the client -> server file copy. Which > client > are you trying to implement that for? > > Hard part is the server -> client anyway ;) > >

Re: [FreeRDP-devel] clipboard filetransfers

2019-02-19 Thread Armin Novak via FreeRDP-devel
Hi, xfreerdp already supports the client -> server file copy. Which client are you trying to implement that for? Hard part is the server -> client anyway ;) regards Armin On 2/19/19 11:06 AM, Alexandr via FreeRDP-devel wrote: > hi all. > i am working on clipboard filetransfers. > now i am i

[FreeRDP-devel] clipboard filetransfers

2019-02-19 Thread Alexandr via FreeRDP-devel
-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 hi all. i am working on clipboard filetransfers. now i am implementing client->server part. looks like i am stuck. i can't find a way to convert FILEDESCRIPTOR obtained by cliprdr_parse_file_list to CLIPRDR_FILE_CONTENTS_REQUEST used by ClientFileCo

Re: [FreeRDP-devel] clipboard filetransfers

2019-01-21 Thread Alexandr via FreeRDP-devel
-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 В Пн, 21/01/2019 в 17:43 +0100, Armin Novak via FreeRDP-devel пишет: > Hi Alexandr, > > > client to server transfer is implemented in xfreerdp > > How it works can be found in the [MS-RDPECLIP] spec. > > > Basically, you announce a list of files

Re: [FreeRDP-devel] clipboard filetransfers

2019-01-21 Thread Armin Novak via FreeRDP-devel
Hi Alexandr, client to server transfer is implemented in xfreerdp How it works can be found in the [MS-RDPECLIP] spec. Basically, you announce a list of files (with relative paths as names) you then request file content file by file This is the same for client to server as well as server to

[FreeRDP-devel] clipboard filetransfers

2019-01-21 Thread Alexandr via FreeRDP-devel
-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Hi all. we need to implement clipboard file-transfers in our rdp client. Does any api documentation available at all ? What code we can use as reference implementation ? thx in advance. -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEWlDDCYMF8IYr2Fv