First: In my opinion xfreerdps multi-connection feature is a nice proof of concept for how it can be done in remina, and it might also be nice for testing. I do however not see any relevant use cases for it in xfreerdp - it would be a lot simpler and more convenient to start multiple instances.
Returning reasonable exit codes is much more relevant, and it shouldn't be guarded by special options. Why not just say that the program always exits with the exit code of the last thread that terminates? 99.999% there will only one thread anyway. I think it would be most relevant to be able to distinguish the different kinds of basic connectivity problems. I am not sure how suitable the Set Error Info codes are as exit codes, but they probably won't do any harm as long as it is documented somewhere ;-) /Mads eduardo fiss beloni wrote, On 03/03/2011 09:01 PM: > I've been working on the exit codes of xfreerdp. This patch is my first > approach, which returns the errors based on the Set Error Info PDU > ([MS-RDPBCGR] 2.2.5.1.1). > > To do that, I had to implement a "singleton mode", which allows only one > thread running. > > It might not be alright to push, so I'd like some comments on that... > > Thanks > > > Eduardo Fiss Beloni > [email protected] > 55 53 8117 8244 ------------------------------------------------------------------------------ What You Don't Know About Data Connectivity CAN Hurt You This paper provides an overview of data connectivity, details its effect on application quality, and explores various alternative solutions. http://p.sf.net/sfu/progress-d2d _______________________________________________ Freerdp-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/freerdp-devel
