In my jQuery web app I’m using events pretty much.
My component for doing ajax client requests (the name is “comm”) to the server has a queue.
This queue is similar to a Backbone.js collection.
So every time I put a new request object into the collection of “comm”, the comm object gets an “add” event and the “worker” method of “comm” looks, if there is currently an ongoing request. If there is no one, the worker method processes the request and finally, when everything works fine, triggers a “complete” event on the request object.
In this comm component only one request at a time is possible. If I add an request object to “comm” and the “add” event gets triggered and the worker method sees, that there is already a request, than nothing happens.
My question is: In this situation, what is the best approach for handling this unprocessed request object IN REGARD TO “AN EVENT INFRASTRUCTURE”?
Until now I had 2 different approaches:
1) I could do the following: If my ongoing request is finished, the worker method can check if there is an unprocessed request object in the collection and process it. This is simple, no event is envolved.
2) Or something different: If the worker method starts due to an “add” event and sees, that there is already an ongoing request, I could implement something like: “I can not respond adeqately to this add event, I place you back. Please trigger yourself in 200 milliseconds again, maybe I have time then.”
Maybe somebody already had a similar problem and had a very good solution to this?
I think a good approach to this problem would be to implement a “next” event that is fired on the queue. Each time a “complete” event is triggered, it should fire the next event on the queue which then would see if there’s any unprocessed requests and if so picks one according to your logic (I assume FIFO)