[1584] in java-interest
Re: Q:exec function
daemon@ATHENA.MIT.EDU (Thomas Ball)
Fri Sep 8 15:31:42 1995
Date: Fri, 8 Sep 1995 09:50:13 -0700
From: Thomas.Ball@Eng.Sun.COM (Thomas Ball)
To: meessen@cppm.in2p3.fr
Cc: java-interest@java.Eng.Sun.COM
The exec() method has been reimplemented for beta, and addresses the
concerns you raised.
Tom
----- Begin Included Message -----
From daemon@java Fri Sep 8 02:16:56 1995
X-Sender: meessen@marul3.in2p3.fr
Mime-Version: 1.0
To: java-interest@java.Eng.Sun.COM
Subject: Q:exec function
X-Info: To unsubscribe, send 'unsubscribe' to java-interest-request@java.sun.com
I may have misunderstood the exec function usage but I suspect a limitation.
It seams impossible to redirect simultaneously stdin stdout and stderr
of the execed system function.
Nothing is said about the asynchronous behaviour of this function.
Does these exec execin execout calls block until system function completion ?
What about the output file streams then ?
When do we write into it or read form it ?
If the exec is asynchronous how do we know when it is finished, and the
return status ?
Apparently exec is already very usefull and very simple and straight forward
in usage.
But and exec function allowing to start a system function and allowing to
redirect simultaneously stdin stdout and stderr would be more general.
This would allow to use java as interface for any curently existing
character oriented application. This is naturaly just for a local usage.
Java should inherit the unix pipe and redirection capabilities.
Bien cordialement,
Ch.Meessen
-
Note to Sun employees: this is an EXTERNAL mailing list!
Info: send 'help' to java-interest-request@java.sun.com
----- End Included Message -----
-
Note to Sun employees: this is an EXTERNAL mailing list!
Info: send 'help' to java-interest-request@java.sun.com
