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 Mick Semb Wever ([EMAIL PROTECTED]) at 06/06/2008 14:16 *Reasons for the changes* *Comments* - By Mick Semb Wever - 06/06/2008 14:16 --- "This code isn't so much in handling server overload but about being a little more intelligent about queuing requests. Requests *must* be synchrnoised, ie queued, against the user's session. This is due to the datamodel holding state related to the current request, implicitly and through its current ControlLevel. Requests between two separate browsers will have different sessions. So the page loading isn't an issue there. But within two separate tabs both reloaded/refreshed the tab that is first reloaded, under the circumstance that there's a previous request still jamming everything up, then it will get dropped immediately and only the second tab will wait in queue. In this situation most likely the jam is serious and the second tab will time out and result in a 409 error. At least only one tab is waiting, that's the main point here, as the server's resources can climb quickly here with requests all waiting while the user hits refresh over and over again."
_______________________________________________ Kernel-issues mailing list [email protected] http://sesat.no/mailman/listinfo/kernel-issues
