Remote Systems
v6.4.1

com.ibm.etools.systems.core
Interface ISystemFileTransferModeRegistry

All Superinterfaces:
ISystemFileTypes
All Known Implementing Classes:
SystemFileTransferModeRegistry

public interface ISystemFileTransferModeRegistry
extends ISystemFileTypes


Field Summary
static String Copyright
           
static String[] DEFAULT_BINARY_FILE_EXTENSIONS
           
static String[] DEFAULT_ISERIES_LPEX_TEXT_FILE_EXTENSIONS
           
static String[] DEFAULT_LPEX_TEXT_FILE_EXTENSIONS
           
static String[] DEFAULT_TEXT_FILE_EXTENSIONS
           
static String[] DEFAULT_TEXT_FILE_NAMES
           
static String[] DEFAULT_UNIX_LPEX_TEXT_FILE_EXTENSIONS
           
 
Method Summary
 ISystemFileTransferModeMapping[] getModeMappings()
           
 boolean isBinary(IFile file)
           
 boolean isText(IFile file)
           
 
Methods inherited from interface com.ibm.etools.systems.core.archiveutils.ISystemFileTypes
isBinary, isBinary, isText, isText
 

Field Detail

Copyright

public static final String Copyright
See Also:
Constant Field Values

DEFAULT_TEXT_FILE_NAMES

public static final String[] DEFAULT_TEXT_FILE_NAMES

DEFAULT_TEXT_FILE_EXTENSIONS

public static final String[] DEFAULT_TEXT_FILE_EXTENSIONS

DEFAULT_LPEX_TEXT_FILE_EXTENSIONS

public static final String[] DEFAULT_LPEX_TEXT_FILE_EXTENSIONS

DEFAULT_ISERIES_LPEX_TEXT_FILE_EXTENSIONS

public static final String[] DEFAULT_ISERIES_LPEX_TEXT_FILE_EXTENSIONS

DEFAULT_UNIX_LPEX_TEXT_FILE_EXTENSIONS

public static final String[] DEFAULT_UNIX_LPEX_TEXT_FILE_EXTENSIONS

DEFAULT_BINARY_FILE_EXTENSIONS

public static final String[] DEFAULT_BINARY_FILE_EXTENSIONS
Method Detail

getModeMappings

public ISystemFileTransferModeMapping[] getModeMappings()

isBinary

public boolean isBinary(IFile file)

isText

public boolean isText(IFile file)

Remote Systems
v6.4.1

Copyright © 2005 IBM Corp. All Rights Reserved.

Note: This documentation is for part of an interim API that is still under development and expected to change significantly before reaching stability. It is being made available at this early stage to solicit feedback from pioneering adopters on the understanding that any code that uses this API will almost certainly be broken (repeatedly) as the API evolves.