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 -> 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 FILEDESCRIPTOR list you extract with the
>> function you mentioned (file name, access rights, ...)
> 
>> -> From that present some file system level view (fuse?) and post the
>> paths to the local clipboard.
> 
>> -> when a file is pasted (fuse read function?) request
> 
>>   -> File size first (ClientFileContentsRequest with the size flag)
> 
>>   -> Data in ServerFileContentsResponse
> 
>>   -> Repeat with ClientFileContentsRequest range flag
> 
>>   -> Data in ServerFileContentsResponse
> 
> 
>> regards
> 
>> Armin
> 
> 
> i do not need direct relation with local filesystem at all, in contrary
> what we developing is kind of gateway, for large number of concurrent
> clients (>1000).
> So i need to implement some way to bypass file chunks directly to
> gateway client.
> For now i am stuck on getting
> CLIPRDR_FILE_CONTENTS_REQUEST.streamId, FILEDESCRIPTOR obtained by
> cliprdr_parse_file_list does not contain it.
> Does any helper function to get one exists ?, or i need to parse
> clipboard_data message by hand ?, i have read clipboard protocol
> document from microsoft, it does not look to hard to do it manually.
> 
> 
> 
> _______________________________________________
> FreeRDP-devel mailing list
> FreeRDP-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/freerdp-devel
> 


_______________________________________________
FreeRDP-devel mailing list
FreeRDP-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freerdp-devel

Reply via email to