| org.continuent.sequoia.common.protocol |
|
Utilitary protocol tools.
|
| Java Source File Name | Type | Comment |
| ByteArrayBlob.java | Class | The representation (mapping) in the Java TM
programming language of an SQL BLOB value. |
| ByteArrayBlobOutputStream.java | Class | This class defines a BlobOutputStream. |
| CommandCompleted.java | Class | This exception is used by the controller to signal the driver from the
successful completion of a command. |
| Commands.java | Class | Protocol commands between Sequoia driver (client) and controller (server).
All communications follow a classic RPC scheme: the driver sends a Command
code, followed by argument(s) for some of the commands, and expects some
answer(s), at the very least an error code or an exception. |
| Field.java | Class | Field is our private implementation of ResultSetMetaData,
holding the information for one column. |
| PreparedStatementSerialization.java | Class | This class contains the data used to serialize PreparedStatement. |
| SQLDataSerialization.java | Class | This class defines Serializers for SQL Data: per type serialization +
deserialization methods and information wrapped in one object. |
| StringClob.java | Class | The representation (mapping) in the Java TM
programming language of an SQL CLOB value. |
| TypeTag.java | Class | This class implements protocol type tags with an internal String, but offers
an abstract interface on top of it in order to be transparently substituted
some day (with enums for instance).
Advantages of using string types is human-readability (debugging, trace
analysis, etc.) and earlier detection in case of protocol corruption.
Drawback maybe a small performance cost.
Check "the importance of being textual" - by Eric S. |