|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
amqsputc fails |
« View previous topic :: View next topic » |
Author |
Message
|
mqjeff |
Posted: Tue Dec 09, 2014 1:31 pm Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008 Posts: 17447
|
Client mode is not usually refered to as bindings, even though in theory the client application is bound to the client libraries.
In fact, the client application is *linked* to the client libraries, and all functions of the client libraries takes place fully within the client application space.
This is why most people refer to client and bindings applications, rather than client-bindings and server-bindings.
And, again, there are *two* kinds of server-binding applications - at least on distributed. There is normal bindings mode, which uses shared memory segments to access pieces of the queue manager. Then there is fastpath bindings, which is tightly coupled into the queue manager processes and access the memory more directly.
Then you get into things on zOS like you have with CICS transactions that never actually connect to a queue manager at all, they merely open/close objects and send or receive messages. I'd almost argue that this is a fourth type of application binding.
You know, since we're being expressive on the subject. |
|
Back to top |
|
 |
PeterPotkay |
Posted: Tue Dec 09, 2014 2:04 pm Post subject: |
|
|
 Poobah
Joined: 15 May 2001 Posts: 7722
|
For server-bindings, there are actually 3 types: Standard, Isolated and FastPath. _________________ Peter Potkay
Keep Calm and MQ On |
|
Back to top |
|
 |
|
|
|
You cannot post new topics in this forum You cannot reply to topics in this forum You cannot edit your posts in this forum You cannot delete your posts in this forum You cannot vote in polls in this forum
|
|
|
|