![]() ![]() ![]() ![]() ![]() ![]() |
Initiating On-Demand Conversion
On-Demand Conversion and Xerces Parser XML Validation
Initiating Automatic Conversion
Automatic Conversion and Xerces Parser XML Validation
Mapping XML To and From FML/FML32 Field Types
Coding Switch Element Routines
Adding a New Buffer Type to tm_typesw
Compiling and Linking Your New tm_typesw
Compiling and Linking Your New tm_typesw for a 16-bit Windows Platform
Receiving Command-line Options
Example: Sending an Asynchronous Message with TPNOTRAN | TPNOREPLY
Example: Sending Asynchronous Requests
Programming Interface for the EventBroker
Notification via Unsolicited Message
Notification via Service Call or Reliable Queue
Prerequisites for a Transaction Commit
Selecting Criteria for a Successful Commit
Trade-offs Between Possible Commit Criteria
Advantages of a Multithreaded/Multicontexted ATMI Application
Disadvantages of a Multithreaded/Multicontexted ATMI Application
Client Threads Join Multiple Contexts
Client Threads Switch to an Existing Context
Userlog Maintains Thread-specific Information
How Server-Dispatched Threads Are Used
Bulletin Board Liaison Verifies Sanity of System Processes
System Keeps Statistics on Server Threads
Userlog Maintains Thread-specific Information
Userlog Maintains Thread-specific Information
Is the Task of Your Application Suitable for Multithreading and/or Multicontexting?
How Many Applications and Connections Do You Want?
What Synchronization Issues Need to Be Addressed?
Will You Need to Port Your Application?
Which Threads Model Is Best for You?
Interoperability Restrictions for Workstation Clients
Prerequisites for a Multithreaded ATMI Application
General Multithreaded Programming Considerations
Setting Up Multicontexting at Initialization
Implementing Security for a Multicontexted ATMI Client
Synchronizing Threads Before an ATMI Client Termination
Coding Rules for Transactions in a Multithreaded/Multicontexted ATMI Application
Coding Rules for Server-Dispatched Threads in Multicontexted ATMI Server
Initializing and Terminating ATMI Servers and Server Threads
Associating Application Threads with a Context
Associating Application Threads with an Existing Server-Dispatched Context
Associating Application Threads with Application-Created Context
Code Rules for Application-Created Thread of an ATMI Server in Application-Created Context
Coding Rules for a Multithreaded ATMI Client
Initializing an ATMI Client to Multiple Contexts
Context State Changes for an ATMI Client Thread
Getting Replies in a Multithreaded Environment
Using Environment Variables in a Multithreaded and/or Multicontexted Environment
Improper Use of the TPMULTICONTEXTS Flag to tpinit( )
Calls to tpinit( ) Without TPMULTICONTEXTS
Insufficient Thread Stack Size
![]() ![]() ![]() |