RE: Design for data queue-driven subsystem

Thanks, Chris. Just knowing that I'm not massively underestimating the
pieces needed to make this work sets my mind at ease.

> -----Original Message-----
> From: Chris Bipes
> 
> We have something similar to what you are looking for.  It is 
> an on-line
> transaction processing system.  We have a data area that hold 
> the control
> values for min number of server, Thresh hold, max number of 
> server, max time
> on queue.  When the server program reads an entry on queue, 
> it checks the
> time stamp of when placed on queue.  If the time is exceeded, 
> it submits a
> request to a monitoring program, waiting on another queue, to 
> start another
> server.  The monitoring program uses system API's to see how many
> occurrences are currently active and start another process if 
> the max is not
> reached.  If the thresh hold is reached, it can notify us that we are
> falling behind.  The monitoring program can be written to 
> handle multiple
> data queue base servers.
NOTICE: This E-mail may contain confidential information. If you are not
the addressee or the intended recipient please do not read this E-mail
and please immediately delete this e-mail message and any attachments
from your workstation or network mail system. If you are the addressee
or the intended recipient and you save or print a copy of this E-mail,
please place it in an appropriate file, depending on whether
confidential information is contained in the message.