[Koha-bugs] [Bug 15147] New: Blocking Calls in Patron Search

[bugzilla-daemon at bugs.koha-community.org]

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=15147

            Bug ID: 15147
           Summary: Blocking Calls in Patron Search
 Change sponsored?: ---
           Product: Koha
           Version: master
          Hardware: All
                OS: All
            Status: NEW
          Severity: enhancement
          Priority: P5 - low
         Component: Circulation
          Assignee: koha-bugs at lists.koha-community.org
          Reporter: martin.renvoize at ptfs-europe.com
        QA Contact: testopia at bugs.koha-community.org
                CC: gmcharlt at gmail.com, kyle.m.hall at gmail.com

Patron search is just plain slow since the whole converting datatables to ajax.

This is because the main route into searching for patrons is the top search
box, and that search in fact fires a series of blocking requests instead of
asynchronous ones.

This can be seen clearly from the chrome dev tools networks tab.  One long
running request to members.pl followed by a non-trivial call to svc/search.

This is fine once, but if you then change the search term inside that top box,
the whole procedure is fired again.

We were better off before the Async work as the search was done as part of the
initial members.pl piece. The page was slow to load, but at least it yielded
results straight away rather than having to fire a second request only after
the page had loaded.

The best solution would be to do it properly asynchronously. Load member.pl
only once in the lifetime of a session perhaps and utilise caches to keep it
clientside.. then a search would always just fire the svc call and thus yield a
much faster search experience.

There are a bunch of places were doing async totally wrong, but this to me is
the most obvious and the one that's hurting our customers the most.

-- 
You are receiving this mail because:
You are the assignee for the bug.
You are watching all bug changes.