Activity report on *[JIRA] Improvement SKER4321 - Load reducing filter that handles only current and last request from client*
Scarab Link: http://sesat.no/scarab/issues/id/SKER4321 Module: Sesat> Kernel Activity generated by Håvard Frøiland ([EMAIL PROTECTED]) at 06/10/2008 10:04 *Reasons for the changes* *Comments* - By Håvard Frøiland - 06/10/2008 10:04 --- "There was no queue but a mob of requests that would try to take the lock and run their request. So in other words it was random who came next if there was someone holding the session's lock. (I have tried to check this up, there could be that there was a strict ordering of waiting threads, but I don't think so) Instead of using a queue at all I think it is better to use a stack, since we really want the last request the user have done to be executed first. And add some limits on how many request a session can have instead of dropping everything between the first and the last. And we also want to keep the timeout. The test implementation I have now goes like this: - A request comes inn, if there is less then max number on the stack then push it, else return 409. (what about max number of 5) - If the current thread's request is the same request as the one at the top of the stack, then execute it. If not then wait for a minimum time to see if our request is at the top of the stack. If this is not the case we return a 409. (timeout)"
_______________________________________________ Kernel-issues mailing list [email protected] http://sesat.no/mailman/listinfo/kernel-issues
