results in the socket getting closed. so the remote process never
completes - it hangs waiting for an EOF - or it ends when I
close the
stream, but I can't read its output because the socket gets closed.
rock and a hard place, so to speak :)
You're not between a rock and a hard
Message-
From: Daniel F. Savarese [mailto:dfs;savarese.org]
Sent: Wednesday, October 30, 2002 9:54 AM
To: [EMAIL PROTECTED]
Subject: Re: [net] Re: problem with RCommandClient
results in the socket getting closed. so the remote process never
completes - it hangs waiting for an EOF
well, it just seemed that by default RCommandClient did not work as one
would expect. but I'm happy with the subclassing approach - it works
You're probably right that at least RExecClient and RCommandClient
should allow for half duplex connections, and as you indicated,
it's not a major
On Wed, 30 Oct 2002, Daniel F. Savarese wrote:
[SNIPPED]
I think what we ought
to do is freeze the code and get evertyhing in shape to meet the
requirements to become a Commons proper project, make a formal 1.x.x
release to supercede NetComponents 1.3.8, and then talk about cutting off
yeah, sorry, it is j-c-net.
-Original Message-
From: Henri Yandell [mailto:bayard;generationjava.com]
Sent: Tuesday, October 29, 2002 2:55 PM
To: Jakarta Commons Developers List
Subject: [???] Re: problem with RCommandClient
Not to be mean, but could you prefix the mail
