Is FTPClient optimized to reuse open connections?

[Talib Jockey]

I am using org.apache.commons.net.ftp.FTPClient class to connect to a remote server for FTP.

My doubt is that if I connect to the FTP Server using ftp.connect(), where ftp is a object of class FTPClient, I dont explicitly call ftp.disconnect() and again try connecting to the FTP Server through ftp.connect(), will it reuse the connection if it has not timedout?

The catch is that I create a new FTPClient object each time I call connect(), somethin like this..

FTPClient ftp = null;
ftp = new FTPClient();
ftp.connect();
ftp = new FTPClient();
ftp.connect();

Will it physically connect each time, or FTPClient(It uses Socket to connect) is optimized to reuse an exisitng open connection, inspite of the fact that I am creating a new object of FTPClient() each time?

[Jan Cumps]

If you use it's default configuration, FTPClient will use this class to create your connection:
DefaultSocketFactory.java.

It just uses java's standard java.net classes to open a connection. No caching or reuse involved.

Regards, Jan

(edit: I said cashing in stead of caching)
[ March 03, 2007: Message edited by: Jan Cumps ]

[Talib Jockey]

Thanks Jan!

So each time a new Socket object is created i.e. it will physically connect to the Server (I connect in the passive mode). Is that right?

[Jan Cumps]

Yes.

Regards, Jan