Remote Systems
v6.4.1

com.ibm.etools.systems.files
Interface SystemFileAPIProvider

All Superinterfaces:
IAdaptable, ISystemViewInputProvider
All Known Implementing Classes:
SystemFileAPIProviderImpl, SystemFileSubSystemAPIProviderImpl, SystemFileSubSystemFactoryAPIProviderImpl

public interface SystemFileAPIProvider
extends ISystemViewInputProvider

Where to start when looking to traverse a remote file system

See Also:
SystemFileAPIProviderImpl

Field Summary
static String copyright
           
 
Method Summary
 int getConnectionCount()
          Return a count of all connections which have at least one subsystem that implements/extends RemoteFileSubSystem
 SystemConnection[] getConnections()
          Return all connections which have at least one subsystem that implements/extends RemoteFileSubSystem
 boolean isDirectoriesOnly()
          Get the directories-only mode.
 
Methods inherited from interface com.ibm.etools.systems.core.ui.view.ISystemViewInputProvider
getAdapter, getConnectionChildren, getShell, getSystemViewRoots, getViewer, hasConnectionChildren, hasSystemViewRoots, setShell, setViewer, showActionBar, showActions, showButtonBar, showingConnections
 

Field Detail

copyright

public static final String copyright
See Also:
Constant Field Values
Method Detail

isDirectoriesOnly

public boolean isDirectoriesOnly()
Get the directories-only mode.


getConnections

public SystemConnection[] getConnections()
Return all connections which have at least one subsystem that implements/extends RemoteFileSubSystem


getConnectionCount

public int getConnectionCount()
Return a count of all connections which have at least one subsystem that implements/extends RemoteFileSubSystem


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.