Acq+Vandelay : more aggressive streamed response throttling
authorBill Erickson <berick@esilibrary.com>
Tue, 21 Feb 2012 15:56:38 +0000 (10:56 -0500)
committerBill Erickson <berick@esilibrary.com>
Tue, 21 Feb 2012 15:56:38 +0000 (10:56 -0500)
commitb50a6b37fe3e8b2817b5bd24252584c94144186f
treecf62fc7011b56968bb5c560e38d9c981bef28a5a
parent0ba3f8f3dd921b3491d3e0280274c50b0f703e9c
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>
Open-ILS/src/perlmods/lib/OpenILS/Application/Acq/Order.pm