|
Michael Ryan wrote: > I do that sort of thing by having one receiving data queue that all the > clients send to, and multiple data queues that the server responds to the > client. I have the client create the data queue (if it doesn't already > exist), and pass the name of that queue to the server. The data queue name > is usually based on the client job number. That's one way to do it ... the extra io of creating the data queues, imho, makes using a keyed data queue a better option. But that's just my opinion. david
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.