Open topic with navigation

# Request/Reply with Inbox Token

In the request/reply communication model, cooperating programs use a token identifying an inbox for one-to-one communication to the inbox. The program that creates the inbox also creates the token and transmits the token, as needed, to request a message be sent to the inbox.

If inboxes are used with entitlements and permissions, requests must have publish and subscriber permissions. Replies require publish permission.

The following diagram illustrates a request/reply interaction.

- The ServerProgram creates a SubscriberObject to request messages from clients and a PublisherObject to reply.

- The RequesterClient program creates an Inbox subscriber object to receive replies from the ServerProgram.

The message flow follows.

1. The RequesterClient initiates the request from EP1 and includes the request and inbox token.

2. The ServerProgram uses the token to send a one-to-one reply message to the Inbox at the RequesterClient.

Figure 10: Request and Token for Inbox Communication

Did you find this helpful?

Yes No
Great!
Thanks for taking the time to give us some feedback.
Sorry about that

Why wasn't this helpful? (check all that apply)

Could not find what I was looking for
Instructions confusing or unclear
Instructions did not work

Want to tell us more?

Please select at least one option or provide details about the issue!!

Error occurred while submitting feedback.

Error2 occurred while submitting feedback.

TIBCO FTL® - Enterprise Edition

Copyright © 2009-2024. Cloud Software Group, Inc. All Rights Reserved.