Hi, On Fri, Nov 21, 2014 at 12:33 PM, Mike Rylander <[email protected]> wrote: > Perhaps we should use a streaming response to the client once checkin is > complete enough to know what routing information there is to know, and then > follow up with a complete (or exception) once the fine disposition is > handled. For SIP, the Evergreen driver can respond immediately upon receipt > of the first message, ignoring the remainder, and the staff client can > update the UI as information flows back. Then, the benefits of Dan's Plan > #1 are realized, and we gain reduced latency for SIP and friends.
Makes sense to me at first blush. Regards, Galen -- Galen Charlton Manager of Implementation Equinox Software, Inc. / The Open Source Experts email: [email protected] direct: +1 770-709-5581 cell: +1 404-984-4366 skype: gmcharlt web: http://www.esilibrary.com/ Supporting Koha and Evergreen: http://koha-community.org & http://evergreen-ils.org
