Why does a Channel with HTTP Transport have a "publish/subscribe" Channel Type?Shouldn't the Channel Type be "request/reply" for a HTTP Channel?
Article ID: KB0092125
Updated On:
| Products | Versions |
|---|---|
| TIBCO IntegrationManager | - |
| Not Applicable | - |
Description
Resolution:
Publish/subscribe channels are used by job creators, while request/reply channels are only used by the request/reply task.
We could have called the channel type send/receive to be more generic, but we chose a name that was more RV oriented.
Publish/subscribe channels are used by job creators, while request/reply channels are only used by the request/reply task.
We could have called the channel type send/receive to be more generic, but we chose a name that was more RV oriented.
Issue/Introduction
Why does a Channel with HTTP Transport have a "publish/subscribe" Channel Type?Shouldn't the Channel Type be "request/reply" for a HTTP Channel?
Environment
Product: TIBCO IntegrationManager
Version: 4.5.0
OS: All
--------------------
Feedback
Yes
No
Powered by
