|
Let me see if I got this right. I may have the client and server names reversed, but hopefully, other than that, the concept is sound. You have multiple client jobs talking to one server job. The client jobs all send data into one data queue for use by the server job. The server job then sends data out to various data queues for use by each of the client jobs. Right? Why not just use two data queues? One for the server and one for all clients? And make the client queue a keyed data queue? And each spawned client job could generate it's own UUID. Send that along with the data request to the server data queue and then the server data queue could write to the client data queue with the UUID as the key. You might even be able to get by with one data queue with the server using it's own UUID. Rob Berendt
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.