Remote Systems
v6.4.1

com.ibm.etools.systems.dstore.core.client
Class ClientUpdateHandler

java.lang.Object
  extended byjava.lang.Thread
      extended bycom.ibm.etools.systems.dstore.core.model.Handler
          extended bycom.ibm.etools.systems.dstore.core.model.UpdateHandler
              extended bycom.ibm.etools.systems.dstore.core.client.ClientUpdateHandler
All Implemented Interfaces:
Runnable

public class ClientUpdateHandler
extends UpdateHandler

The ClientUpdateHandler is contains a queue of data update requests and periodically sends out domain notifications to domain listeners


Field Summary
static String Copyright
           
 
Fields inherited from class com.ibm.etools.systems.dstore.core.model.UpdateHandler
_dataObjects
 
Fields inherited from class com.ibm.etools.systems.dstore.core.model.Handler
_dataStore, _waitIncrement
 
Fields inherited from class java.lang.Thread
MAX_PRIORITY, MIN_PRIORITY, NORM_PRIORITY
 
Constructor Summary
ClientUpdateHandler()
          Constructor
 
Method Summary
 void sendKeepAliveConfirmation()
          Does not apply in this case.
 void sendKeepAliveRequest()
          Does not apply in this case.
 void sendUpdates()
          Periodically called to notify domain listeners of updated data from the server
 void updateAppendFile(String path, byte[] bytes, int size, boolean binary)
          Not applicable - this is only applicable on the server side
 void updateAppendFile(String path, byte[] bytes, int size, boolean binary, String byteStreamHandlerId)
          Not applicable - this is only applicable on the server side
 void updateFile(File file, DataElement object)
          Notifies domain listeners that a file has been updated
 void updateFile(String path, byte[] bytes, int size, boolean binary)
          Not applicable - this is only applicable on the server side
 void updateFile(String path, byte[] bytes, int size, boolean binary, String byteStreamHandlerId)
          Not applicable - this is only applicable on the server side
 
Methods inherited from class com.ibm.etools.systems.dstore.core.model.UpdateHandler
clean, clean, handle, update, update, update
 
Methods inherited from class com.ibm.etools.systems.dstore.core.model.Handler
finish, getWaitTime, isFinished, run, setDataStore, setWaitTime
 
Methods inherited from class java.lang.Thread
activeCount, checkAccess, countStackFrames, currentThread, destroy, dumpStack, enumerate, getContextClassLoader, getName, getPriority, getThreadGroup, holdsLock, interrupt, interrupted, isAlive, isDaemon, isInterrupted, join, join, join, resume, setContextClassLoader, setDaemon, setName, setPriority, sleep, sleep, start, stop, stop, suspend, toString, yield
 
Methods inherited from class java.lang.Object
clone, equals, finalize, getClass, hashCode, notify, notifyAll, wait, wait, wait
 

Field Detail

Copyright

public static final String Copyright
See Also:
Constant Field Values
Constructor Detail

ClientUpdateHandler

public ClientUpdateHandler()
Constructor

Method Detail

updateFile

public void updateFile(String path,
                       byte[] bytes,
                       int size,
                       boolean binary)
Not applicable - this is only applicable on the server side

Specified by:
updateFile in class UpdateHandler
Parameters:
path - the path of the file to send
bytes - the bytes to send
size - the number of bytes to send
binary - indicates whether to send the bytes as binary or text

updateAppendFile

public void updateAppendFile(String path,
                             byte[] bytes,
                             int size,
                             boolean binary)
Not applicable - this is only applicable on the server side

Specified by:
updateAppendFile in class UpdateHandler
Parameters:
path - the path of the file to send
bytes - the bytes to send
size - the number of bytes to send
binary - indicates whether to send the bytes as binary or text

updateFile

public void updateFile(String path,
                       byte[] bytes,
                       int size,
                       boolean binary,
                       String byteStreamHandlerId)
Not applicable - this is only applicable on the server side

Specified by:
updateFile in class UpdateHandler
Parameters:
path - the path of the file to send
bytes - the bytes to send
size - the number of bytes to send
binary - indicates whether to send the bytes as binary or text
byteStreamHandlerId - indicates the byte stream handler to receive the bytes

updateAppendFile

public void updateAppendFile(String path,
                             byte[] bytes,
                             int size,
                             boolean binary,
                             String byteStreamHandlerId)
Not applicable - this is only applicable on the server side

Specified by:
updateAppendFile in class UpdateHandler
Parameters:
path - the path of the file to send
bytes - the bytes to send
size - the number of bytes to send
binary - indicates whether to send the bytes as binary or text
byteStreamHandlerId - indicates the byte stream handler to receive the bytes

updateFile

public void updateFile(File file,
                       DataElement object)
Notifies domain listeners that a file has been updated

Parameters:
file - the updated file
object - the element associated with the updated file

sendUpdates

public void sendUpdates()
Periodically called to notify domain listeners of updated data from the server

Specified by:
sendUpdates in class UpdateHandler

sendKeepAliveRequest

public void sendKeepAliveRequest()
Does not apply in this case. Use ClientCommandHandler.sendKeepAliveRequest().

Specified by:
sendKeepAliveRequest in class UpdateHandler

sendKeepAliveConfirmation

public void sendKeepAliveConfirmation()
Does not apply in this case. Use ClientCommandHandler.sendKeepAliveConfirmation().

Specified by:
sendKeepAliveConfirmation in class UpdateHandler

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.