This section describes how to write methods for EAServer-specific APIs, including C routines, accessing SSL client certificates, and issuing intercomponent calls. A C++ method signature must use the return types and parameter datatypes described in “Supported datatypes”. To implement any of the features that require EAServer C routines, you must include jagpublic.h and implement the methods for each feature as follows:
Handling Errors
Use user-defined or CORBA system exceptions to handle errors. See “Error handling” for more information about system and user-defined exceptions.
Caching Connections to Third-Tier Database Servers
You can use a connection cache to improve performance when connecting to database servers. See “Using Connection Manager routines in C, C++, and ActiveX components” for more information.
Returning Result Sets
A component method can return row results to the client. See “Returning result sets” for more information.
Managing explicit OTS transactions
You can explicitly to manage OTS transactions from your component.
Setting Transaction State
Methods in a transactional component should call one of the transaction primitive routines to set the transaction state before returning. See “Methods that set transactional state” for more information.
Sharing Data Between C++ Components
EAServer provides C routines that allow components within the same package to share data with each other. See “Share data between C or C++ components” for more information.
| Copyright © 2005. Sybase Inc. All rights reserved. |
|
|
