RE: This is a software design question - ILE related

[Pete Hall <pbhall@xxxxxxxxxx>]

At 19:02 07/31/2000 , Nathan M. Andelin wrote:
>One technique I've used in the past is to have a single request queue for
>the server, but a unique response queue for each client.  When a client
>makes a request, it also tells the server which queue to respond to.
>
>But, then I begin to wonder whether having all those separate queues and
>calls to QSNDDTAQ and QRCVDTAQ is any more efficient than multiple open data
>paths managed by the OS.

The multiple reply queue and single request queue works well when you have 
small requests and return a (relatively) great amount of data. If you had a 
single reply queue, it would be a constraint. In your case though, with zip 
codes, I would guess that the reply data would be approximately the same 
size as the request data, therefore, it would seem reasonable to use a 
single reply queue also. Could you use a keyed reply queue with the key 
being the job number of the requestor? There might be problems with this if 
you use group jobs, but maybe that wouldn't even be a problem if the 
response time is short.


Pete Hall
pbhall@execpc.com
http://www.execpc.com/~pbhall
+---
| This is the Midrange System Mailing List!
| To submit a new message, send your mail to MIDRANGE-L@midrange.com.
| To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com.
| To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator: david@midrange.com
+---