Hi Mads, I agree to have it in FreeRDP, but I do *not* agree to have it in libfreerdp. That's two different thing. libfreerdp is the core library that implement the core RDP protocol. If SOCKS4 got built in, should SOCKS5? HTTP proxy? SSH tunnel? Unix socket? That's messing up the readibility and the project's structural design.
This should be done as an extension through extensions. We can create a folder extensions/socks4, then the extension should be loaded like this: xfreerdp --ext socks4 --data user:pass -- (server) I can see that the current extension API might not be enough to implement socks4 case, but we can extend it. Please work towards that direction, unless you or anyone have better idea. Thanks, Vic On 04/20/2011 08:52 PM, Mads Kiilerich wrote: > My tentative conclusion is that I would like to see SOCKS support built in. > > /Mads ------------------------------------------------------------------------------ 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
