Hi Mads, On 04/21/2011 12:28 AM, Mads Kiilerich wrote: > But it all follows from how we have tcp.c as a part of libfreerdp and > thus have hardcoded that we use tcp sockets. tcp.c is however also the > part of libfreerdp that has most platform specific code (plus the > ui_select callback - whatever that is intended to do).
Take a look at the very first MS RDP document, [MS-RDPBCGR] section 2.1: "The [MS-RDPBCGR] packets are encapsulated in the Transmission Control Protocol (TCP). The TCP packets MUST be encapsulated in version 4 or 6 of the IP protocol." It's very clearly stated that TCP is the core of the protocol. And it also support the idea that everything else other than tcp or some other proxy layer between tcp and rdp (like socks4 proxy here) is not standard and should be in its own extension plugin. > The best solution would perhaps be to more or less move tcp.c out of > libfreerdp and replace it with ui callbacks. That would also let us get > rid of the not-so-pretty rdp_get_fds and rdp_check_fds. We would however > still have to expose a FD to the TLS layer (apparently). It's possible and feasible to replace tcp or add one layer on top of tcp, through an extension, however that does not mean we should remove tcp from libfreerdp, and the reason is as I said above. Apparently TLS is also part of the RDP core standard. > /Mads Vic ------------------------------------------------------------------------------ Benefiting from Server Virtualization: Beyond Initial Workload Consolidation -- Increasing the use of server virtualization is a top priority.Virtualization can reduce costs, simplify management, and improve application availability and disaster protection. Learn more about boosting the value of server virtualization. http://p.sf.net/sfu/vmware-sfdev2dev _______________________________________________ Freerdp-devel mailing list Freerdp-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freerdp-devel
