|
|
|
|
|
|
Emphasis on the Default Case
The coverage of BEA Tuxedo /Q programming in this topic primarily reflects the left-hand portion of the figure Queued Service Invocation. In the figure, a client (or a process acting in the role of a client) queues a message by calling tpenqueue(3c) and specifying a queue space made available through a TMQUEUE(5) server. The client later retrieves a reply via a tpdequeue(3c) call to TMQUEUE.
The figure Queued Service Invocation shows the queued message being dequeued by the server TMQFORWARD(5) and sent to an application server for processing (via tpcall(3c)). When a reply to the tpcall() is received, TMQFORWARD enqueues the reply message. Because a major goal of TMQFORWARD is to provide an interface between the queue space and existing application services, it does not require further application coding. For that reason, this topic concentrates on the client-to-queue space side.
A brief example of the use of the queued message facility is distributed with the software and is described in A Sample Application.
|
|
|
|
|
|
Copyright © 2000 BEA Systems, Inc. All rights reserved.
|