Hi Ahutosh,
I want to use this applet in Intranet i.e within my office network.
Ok
My major concern is whether using Applet will serve my purpose. As i
have to execute remote scripts in many remote machines and collect and
display their result in one Client Applet.
I've never done it, but I can see no reason why not. Your Applet will have
to be signed if you're connecting to machines other than the "codebase". And
some may argue that an alternate design where the client makes a single
connection to the server (and it is then the server that makes (or
maintains) the numerous connections to the "many remote machines" and
packages up the result for the client) may be a better approach. But who
knows? Give it a go.
My take on it is that one's encrypted and the other isn't. If encryption and
host authentication is an issue in your intranet then use SSH or IPsec, but
I doubt that yours would be the first application to be transmitting data
and passwords in-the-clear within the firewalls.
How many clients are you expecting to be running this thing simultaneously?
Are you happy with one-process/client on the server?
How many commands will make up a session? Leaving all the links up or
disconnecting for each request?
As I said previously, I've never written an Applet that talks RSH (apart
from the initial handshake, how hard can it be?) but I have written Applets
that talk to the server via TCP/IP sockets and I can assure you they are the
Dog's Bollocks!
Cheers Richard Maher