Rational Developer for Power Systems Software
V7.6

com.ibm.etools.iseries.subsystems.qsys.cache
Class CacheFileSystemHelpers

java.lang.Object
  extended by com.ibm.etools.iseries.subsystems.qsys.cache.CacheFileSystemHelpers

public class CacheFileSystemHelpers
extends Object


Field Summary
static String copyright
           
 
Method Summary
protected static void assertCacheSize()
          Ensure the cache size is less than the user specified maximum size
static boolean clearCache(Shell shell, File cacheLocation, boolean confirmationRequired)
          Clear the remote systems cache.
static long getCacheSize(File file)
          Calculates the total size of the cache.
 
Methods inherited from class java.lang.Object
clone, equals, finalize, getClass, hashCode, notify, notifyAll, toString, wait, wait, wait
 

Field Detail

copyright

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

clearCache

public static boolean clearCache(Shell shell,
                                 File cacheLocation,
                                 boolean confirmationRequired)
Clear the remote systems cache.

Parameters:
confirmationRequired - If true, the user is first prompted if they really wish to clear the cache. Otherwise, the cache is cleared without any user intervention.
Returns:
true if the cache was cleared, false if it was not.

getCacheSize

public static long getCacheSize(File file)
Calculates the total size of the cache.

Parameters:
file - The root directory for the cache.
Returns:
The combined size (in bytes) of all files in the directory file and all subdirectories.

assertCacheSize

protected static void assertCacheSize()
Ensure the cache size is less than the user specified maximum size


Rational Developer for Power Systems Software
V7.6

Copyright 2011 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.