Using Conversational Messaging with the TEDG


	BEA Home \| Events \| Solutions \| Partners \| Products \| Services \| Download \| Developer Center \| WebSUPPORT
	http://www.oracle.com/technology/documentation/index.html \| Site Map \| Search \| PDF Files \| Contact \| Glossary

Tuxedo Documentation \| Using the BEA Tuxedo TOP END Domain Gateway \| Local Topics \| Previous Topic \| Next Topic \| Contents

The BEA Tuxedo and BEA TOP END systems support different styles of conversational message passing:

The BEA TOP END system supports pseudo-conversations. A BEA TOP END server can indicate that it wants to maintain context (a conversation) with a client at almost any time by setting the TP_APPL_CONTEXT flag. (See tp_server_send(3T) in the BEA TOP END Programmer's Reference Manual for details.)
BEA Tuxedo conversations are much more structured. The administrator configures servers to be conversational and a set of conversational functions used by the client and server establishes a connection and maintains the conversation. BEA Tuxedo conversations are half-duplex meaning that one side of the conversation can send multiple messages before relinquishing control of the connection.

The TEDG provides a mapping of BEA TOP END pseudo-conversations to the BEA Tuxedo conversation model. This mapping enables BEA Tuxedo clients to maintain context with BEA TOP END servers for multiple-step interactions. The reverse is also true for BEA TOP END clients that want to maintain context with BEA Tuxedo servers. Multiple-step interactions are routed to the same server until the conversation is terminated. Single-step interactions between conversational components are also allowed. If you need the same server to handle single-step and multiple-step interactions, then you must use conversational messaging.