Hi,
I have the following requirement, and I am seeking your input.
1. web-based users make requests for data which are put
in a queue
2. these requests and their status need to be in a database
so that users can watch the status of the queue and their
requests in the queue
3. a
Stephen Adkins writes:
QUICK AND DIRTY SINGLE-SERVER SOLUTION
I implemented a quick-and-dirty single-server solution, where
I use a single server to process requests. I simply poll the
request table in the database once a minute for new requests,
and if they exist, I process them.
Now I
Stephen Adkins writes:
The server(s) connect to a mainframe and perform time-consuming,
repetitive transactions to collect the data that has been requested.
Thus, these servers are slow, waiting several seconds for each
response, but they do not put a large load on the local processor.
So I
