Home >> All >> org >> apache >> derby >> impl >> [ drda Javadoc ]

• org.apache.derby.impl.drda: Javadoc index of package org.apache.derby.impl.drda.


Package Samples:

• org.apache.derby.impl.drda

Classes:

• DDMReader: The DDMReader is used to read DRDA protocol. DRDA Protocol is divided into three layers corresponding to the DDM three-tier architecture. For each layer, their is a DSS (Data Stream Structure) defined. Layer A Communications management services Layer B Agent services Layer C Data management services At layer A are request, reply and data correlation, structure chaining, continuation or termination of chains when errors are detected, interleaving and multi-leaving request, reply, and data DSSs for multitasking environments. For TCP/IP, the format of the DDM envelope is 2 bytes Length of the data ...
• DecryptionManager: This class is used to decrypt password and/or userid. It uses Diffie_Hellman algorithm to get the publick key and secret key, and then DES encryption is done using certain token (based on security mechanism) and this side's own public key. Basically, this class is called when using a security mechanism that encrypts user ID and password (eusridpwd). This class uses IBM JCE to do Diffie_Hellman algorithm and DES encryption.
• TestProto: This class is used to test error conditions in the protocol. The protocol to send to the Net server is contained in a file encoded as calls to routines in ddmreader and ddmwriter. Additional commands have been added for testing purposes. To add tests, modify the file protocol.tests. Tests can also be done as separate files and given as an argument to this class.
• EbcdicCcsidManager: A concrete implementation of a CcsidMgr used to convert between Java UCS2 and Ebcdic as needed to handle character DDM Parameters. This implementation only supports converting from the ASCII invariant of UNICODE to Ebcdic. This should be fine since this class is intended for converting DDM Parameter data only.
• DDMWriter: The DDMWriter is used to write DRDA protocol. The DRDA Protocol is described in the DDMReader class. For more details, see DRDA Volume 3 (Distributed Data Management(DDM) Architecture (DDS definition)
• AppRequester: AppRequester stores information about the application requester. It is used so that multiple sessions can share information when they are started from the same version of the application requester.
• CodePointNameTable: This class has a hashtable of CodePoint values. It is used by the tracing code and by the protocol testing code It is arranged in alphabetical order.
• Database: Database stores information about the current database It is used so that a session may have more than one database
• Session: Session stores information about the current session It is used so that a DRDAConnThread can work on any session.
• TestFile: This tests protocol errors and protocol not used by JCC The file containing the test is given as an argument
• DssConstants: This class defines DSS constants that are shared in the classes implementing the DRDA protocol.
• SignedBinary: Converters from signed binary bytes to Java short , int , or long .
• DRDAStatement: DRDAStatement stores information about the statement being executed
• NetworkServerControlImpl: NetworkServerControlImpl does all the work for NetworkServerControl
• DRDAResultSet: DRDAResultSet holds result set information
• CcsidManager
• CharacterEncodings
• ClientThread
• CodePoint
• DRDAConnThread
• DRDAProtocolException
• DRDAProtocolExceptionInfo
• DRDAXAProtocol
• DRDAXid
• DssTrace

Home | Contact Us | Privacy Policy | Terms of Service