Acq+Vandelay : more aggressive streamed response throttling
authorBill Erickson <berick@esilibrary.com>
Tue, 21 Feb 2012 15:56:38 +0000 (10:56 -0500)
committerThomas Berezansky <tsbere@mvlc.org>
Thu, 15 Mar 2012 19:23:54 +0000 (15:23 -0400)
commit1ce564045c24b18919f7ec49d2459b7317190a0f
treee24d49623c7983a194286af72c65dc9d28a952b0
parentde4bcd86cd52c0f787260c3055d0f75b24f561c2
Acq+Vandelay : more aggressive streamed response throttling

With the addition of Vandelay processing, the server now wants to
respond with status information a lot more often when uploading /
process ACQ records.  This patch applies the level of throttling to ACQ
processing as Vandelay uses natively, which starts verbose and quickly
cuts back on chatter as processing continues up to (currently) a
throttle window of 1 delivered response per 256 responses.  Apart from
saving bandwith, this helps alleviate a known problem in the staff
client where long-running, dense streams of multipart responses
eventually stop bubbling up from the browser to the application.
Making the responses more sparse seems to help this a lot.

Signed-off-by: Bill Erickson <berick@esilibrary.com>
Signed-off-by: Ben Shum <bshum@biblio.org>
Open-ILS/src/perlmods/lib/OpenILS/Application/Acq/Order.pm