>For example: Pancho request a report that may process for 2 hours while Maria request a report that can be processed within 2 minutes. The system must be able to continue processing Pancho's report while Maria's report isn't held up for 2 hours.
Jerry shared a follow-up. Users send requests and pointers to a print server list. CR is servicing the reports. One requirement would be to insert Maria's little two-minute job in the middle of Pancho's 2 hr job, and then resume Pancho's job once Marias is fininshed - Right?
This maybe a situation for multi-threaded COM. At time intervals, COM would review the the print server list for requests with higher priority (or shorter durations?). If an appropriate request was identified, COM would push the request the CR controller. CR controller would pause Pancho's job, start Maria's, then restart Pancho's (providing the print server list had no new demands).
Is this kind of what you're thinking about doing?
Imagination is more important than knowledge