| Author |
Message
|
| 547c547 |
 Posted: Tue Sep 08, 2015 3:10 am Post subject: web service doubt |
 |
|
Acolyte
Joined: 16 Jun 2014
Posts: 51
|
Can I receive a request a from web service and keep that request with flow for processing without replying webservice?
HTTPInput -compute -httpreply
HTTP -compute -no reply or acknowledgement
Is there any alternative for this.. Please clarify me? |
|
| Back to top |
|
 |
| nelson |
| Posted: Tue Sep 08, 2015 4:17 am Post subject: |
|
|
Partisan
Joined: 02 Oct 2012
Posts: 313
|
| You can do it, but the client who is requesting the WS, by default will receive a fault message that indicates that the timeout expired... |
|
| Back to top |
|
|
| fjb_saper |
| Posted: Tue Sep 08, 2015 4:30 am Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20768
Location: LI,NY
|
| nelson wrote: |
| You can do it, but the client who is requesting the WS, by default will receive a fault message that indicates that the timeout expired... |
Even on a fire and forget type operation? 
_________________
MQ & Broker admin |
|
| Back to top |
|
|
| nelson |
| Posted: Tue Sep 08, 2015 4:47 am Post subject: |
|
|
Partisan
Joined: 02 Oct 2012
Posts: 313
|
| fjb_saper wrote: |
| nelson wrote: |
| You can do it, but the client who is requesting the WS, by default will receive a fault message that indicates that the timeout expired... |
Even on a fire and forget type operation? |
Is this enough?
| Code: |
<binding ...>
...
<operation name="UpdateStatus">
<soap:operation delivery="fire-and-forget">
<input message="inputMessage"/>
</soap:operation>
</operation>
</binding> |
I've not tested this scenario... |
|
| Back to top |
|
|
| 547c547 |
| Posted: Tue Sep 08, 2015 5:16 am Post subject: |
|
|
Acolyte
Joined: 16 Jun 2014
Posts: 51
|
| nelson wrote: |
| fjb_saper wrote: |
| nelson wrote: |
| You can do it, but the client who is requesting the WS, by default will receive a fault message that indicates that the timeout expired... |
Even on a fire and forget type operation? |
Is this enough?
| Code: |
<binding ...>
...
<operation name="UpdateStatus">
<soap:operation delivery="fire-and-forget">
<input message="inputMessage"/>
</soap:operation>
</operation>
</binding> |
I've not tested this scenario... |
Can we do this with HTTP nodes if yes, how? |
|
| Back to top |
|
|
| Vitor |
| Posted: Tue Sep 08, 2015 5:30 am Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| nelson wrote: |
| You can do it, but the client who is requesting the WS, by default will receive a fault message that indicates that the timeout expired... |
From an HTTPInput node (quoted by the OP)?
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| nelson |
| Posted: Tue Sep 08, 2015 5:39 am Post subject: |
|
|
Partisan
Joined: 02 Oct 2012
Posts: 313
|
|
| Back to top |
|
|
| Vitor |
| Posted: Tue Sep 08, 2015 5:51 am Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
Granted, but if the flow operation is intended to be one-way why would you configure that?
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| Vitor |
| Posted: Tue Sep 08, 2015 5:54 am Post subject: Re: web service doubt |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| 547c547 wrote: |
| Can I receive a request a from web service and keep that request with flow for processing without replying webservice? |
Here's a question - if the "request" from the web service is not intended to receive a replay, what's going to receive the fault? The requestor will have closed the connection and moved on.
The model you're describing is variously described as a "fire and forget" or an "asynchronous" request.
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| fjb_saper |
| Posted: Tue Sep 08, 2015 8:45 am Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20768
Location: LI,NY
|
Jogging my memory here....
Aren't you supposed to return a 204 success code? I'd have to lookup the codes but there is one for success no data... That's the one you're supposed to send back... for a fire and forget call.
So yes in any instance you'll need a reply node... for HTTP... Darn (unreliable) synchronous protocols... 
_________________
MQ & Broker admin |
|
| Back to top |
|
|
|
|
