| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| Single request and multiple responses |
« View previous topic :: View next topic » |
| Author |
Message
|
| muthu121521 |
 Posted: Tue Nov 03, 2015 9:22 am Post subject: Single request and multiple responses |
 |
|
Apprentice
Joined: 31 Aug 2015
Posts: 36
|
Hi All,
I have a requirement where in i need to send the response by splitting it because of the size of the payload .
Through which node i can achieve this functionality ?
Service exposed have to be in https or web service node?
Will using async response node will achieve this functionality ?
has any one worked on similar requirements pls let me know |
|
| Back to top |
|
 |
| mqjeff |
| Posted: Tue Nov 03, 2015 9:35 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 17447
|
HTTP only sends a single response message.
In order for the HTTP requester to get another response, it will need to make another request.
SOAP over JMS and SOAP over HTTP both have this same issue.
_________________
chmod -R ugo-wx / |
|
| Back to top |
|
|
| Vitor |
| Posted: Tue Nov 03, 2015 9:49 am Post subject: Re: Single request and multiple responses |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| muthu121521 wrote: |
I have a requirement where in i need to send the response by splitting it because of the size of the payload .
Through which node i can achieve this functionality ? |
You can't. Request and response are a pair.
| muthu121521 wrote: |
| Service exposed have to be in https or web service node? |
Neither - it won't work.
| muthu121521 wrote: |
| Will using async response node will achieve this functionality ? |
No.
| muthu121521 wrote: |
| has any one worked on similar requirements pls let me know |
Yes.
For a large number of discrete results, typically you send as much of the request as you can (say 50 rows from a database result set containing 1000 rows) with a flag in the response indicating that there's more to come. The requestor then repeats the request, adding a value of "50" so that the requesting service knows to send rows 51-100 and a flag saying "more to come". The process repeats with the last set of rows having a flag saying "we're done". Clearly you can cache the result set to prevent excessive database access.
If the result is one large item (say a JPEG or PDF document), the result can be saved to a file system or other bulk storage and the web service can return with a URL from which it can be retrieved. This requires proper security and other such design, and both solutions have to be implemented in code. Broker does not provide either out of the box.
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| 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
|
|
|
|
