You would not need a new subsystem, just a job queue in an existing one. Interesting thought. Have each job enque an entry in a keyed data queue with the job ID info. The job that waits on the queue pulls the queue entry, then checks the job queue with an API to see if all the jobs are done.

Jim Oberholtzer
Chief Technical Architect
Agile Technology Architects


On 9/12/2011 9:18 AM, James Horn wrote:
could you create a new subsystem and have all jobs be submitted to 1 jobq
which goes to this subsystem.

When both are empty they are complete?

Jim

As an Amazon Associate we earn from qualifying purchases.

This thread ...

Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

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.