JFile v.2 provides three means of transferring data to or from the server: URLConnection, Sockets and WinInet*.
The default transfer method for Windows, Unix or Linux is URLConnection. The default transfer method for MacOS is sockets. URLConnection and WinInet are not available with MacOS. URLConnection does not function correctly with Netscape 6.x. When available (on a Win+IE system only), WinInet is the preferable tranfer method.
Note: In a WinInet download, if more than one of the URLs to download is an https location, JFile will automatically reset the transfer method to URLConnection.
Use the following diagram to determine which transfer method you should use.
| URL Connection (Windows default method) |
Sockets (Mac default method) |
WinInet* |
|---|---|---|
| Can use SSL for encrypted file transfer while executing within the browser. | Cannot use SSL in any context. | Can use SSL for encrypted file transfer from Windows/IE client. |
| Does not show accurate progress indicator. Since browser buffers output, transfer counter goes to 100% and then waits while the actual transfer is executed. | Shows accurate transfer progress indicator. | Shows accurate transfer progress indicator |
| Uses memory inefficiently for large transfers (> 50 MB). | Efficient for large transfers (unlimited). | Efficient for large transfers (unlimited). |
| Can be used with supported versions of Windows IE or Netscape. | Can be used with supported versions of Windows IE, Windows Netscape or Macintosh IE (JFile automatically switches to sockets connection if the upload is from a Macintosh client or Netscape 6.x). | Can be used only with Windows/IE client. |
| Can be used when client is accessing web site through an authenticating proxy. | Cannot be used with authenticating proxy. | Can be used with authenticating proxy. (requires sending empty request first. See WinInetNTLM parameter). |
*WinInet transfer is not available in version 1.x.
See also UseSockets, setTransferMethod, UseWinInet, and autoSetTransferMethod.