| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| Reply to an address other than the HTTP-request originator ? |
« View previous topic :: View next topic » |
| Author |
Message
|
| harelmoshe1 |
 Posted: Mon Mar 13, 2006 7:09 am Post subject: Reply to an address other than the HTTP-request originator ? |
 |
|
Apprentice
Joined: 29 Dec 2005
Posts: 41
|
Is it possible to have a flow of the form:
HTTPInput --> ... --> HTTPReply
in which the reply is done to an address other than the one who generated the HTTP request ?
If so, i'll be glad to know how or referred to a thread dealing with this issue (since i didn't found one yet)...
Thank,
Harel |
|
| Back to top |
|
 |
| jefflowrey |
| Posted: Mon Mar 13, 2006 7:13 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
HTTP is a synchronous protocol. When the request is made, a fixed TCP/IP connection is established between the requestor and the replier. The requester is blocked on that connection until the reply comes back.
You can create a flow that looks like HttpInput-->...-->HttpRequest-->HttpInput -->...-->HttpReply... but if you don't ever send a reply back to the original requester, then they will always get a timeout error and think that your service is not working.
What are you trying to do?
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
| harelmoshe1 |
| Posted: Mon Mar 13, 2006 8:10 am Post subject: ... |
|
|
Apprentice
Joined: 29 Dec 2005
Posts: 41
|
I'm trying to handle the following scenario:
One user sends XML data to my WBI web-service, and the message sometimes cannot be forwarded in the flow for some reason. What i want is to 'resend' the message by a flow which sends the same XML sent by the user to the same WS he originally tried to access, but - send the response back to him instead of the flow who resent the message on his behalf.
Any workarounds ? maybe 'playing' with the request-identifier somewhere ? |
|
| Back to top |
|
|
| JLRowe |
| Posted: Tue Mar 14, 2006 9:11 am Post subject: |
|
|
Yatiri
Joined: 25 May 2002
Posts: 664
Location: South East London
|
This is what would be described as a callback, always do a HTTPReply to the original request, and then callback the client (preferably using some address that they passed earlier) at a later time.
There is a web service standard that handles these situations, called WS-Addressing. |
|
| Back to top |
|
|
|
|
|
| |
|
Page 1 of 1 |
|
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
|
|
|
|
