There's really no advantage to having it be asynchronous, and since
TigerVNC, RealVNC, and others have adopted the synchronous approach, it
makes sense for us to do likewise.
On 5/10/13 3:18 PM, Kevin Van Workum wrote:
I would find that helpful. Currently I'm forced to scan the log file to
I noticed that vncconnect's exit status is true if it can connect to the
vncserver even though the connection to the viewer could not made. The
server knows that the connection to the viewer was not established as
evidenced by the connection failed: Connection refused message in its log
file. Is
I would find that helpful. Currently I'm forced to scan the log file to
determine success of the connection on the server side. Maybe you could
keep the asynchronous behavior default and just add a -sync option to
request a synchronous connect instead? Either way.
On Fri, May 10, 2013 at 4:05
