Hi,
Thanks for your replies.
The client code is not currently pushed online.
I have made my best to use the WinPR APIs to have portable code. On mstsc,
I guess it could use NamedPipes to simulate the equivalent of the Unix
domain socket.
Regarding the Windows code that uses the channel created by
Hi Thomas,
Do you have the code available on a branch somewhere? I'm curious about
this virtual channel. Is it portable to Windows, and could it be possibly
ported to mstsc? If the virtual channel is custom and not really usable to
others, I think it's better off made as a separate virtual channel
Hi Bernard,
github.com/awakecoding/RdpChannel is a repo where I developed sample
virtual channel clients and servers that are portable between FreeRDP and
mstsc/Windows.
As for the request of including extra virtual channels, why not? Just make
it as clean, extensible and reusable to others from
Hi Thomas,
On Mon, Feb 09, 2015 at 04:15:13PM +0100, Thomas Calderon wrote:
> Only the client code is implemented within FreeRDP.
What would the server side then be? Is this available freely somewhere or
part of an product?
> Is there a policy regarding accepting a new channels within the upstrea
Le 09/02/2015 16:15, Thomas Calderon a écrit :
> Dear list,
>
> I have been working on implementing a new channel within FreeRDP.
> Only the client code is implemented within FreeRDP.
> It can be summarized as a Unix socket producer/consumer.
> This allows to serialize any protocol operating over a
Dear list,
I have been working on implementing a new channel within FreeRDP.
Only the client code is implemented within FreeRDP.
It can be summarized as a Unix socket producer/consumer.
This allows to serialize any protocol operating over a Unix socket and can
be very convenient to expose services
