I have some queries which can take over a second to execute. It is likely that there will be multiple queries per HTTP request and often several can be queried at once with no appreciable additional processing time.
To implement this, I have created a BatchQuery class who's constructor accepts an array of RequestObjects. The BatchQuery's constructor will create a QueryObject for each RequestObject unless a QueryObject has already been created for a previous RequestObject which meets the l
Don't worry, I understood the request thing.
I was thinking along the lines of wanting to execute queries either (a) in the order they arrive in, as in request #1's queries should probably begin being executed before request #2's if that's not done concurrently, or (b) according to an undescribed priority system, like where one client/request may have a higher priority than another based on something, or that certain queries are innately more important than others.
The required order