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

bugzilla-daemon at bugs.koha-community.org bugzilla-daemon at bugs.koha-community.org
Fri Nov 6 16:56:43 CET 2015


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

Jonathan Druart <jonathan.druart at bugs.koha-community.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |jonathan.druart at bugs.koha-c
                   |                            |ommunity.org

--- Comment #1 from Jonathan Druart <jonathan.druart at bugs.koha-community.org> ---
(In reply to Martin Renvoize from comment #0)
> 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.

I see only 1 request to svc/search, what are the others?

> 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 idea was to use the top box to launch the first search, then use the
filters on the left when you are on the result page to refine the search.

> 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.

What do you want to cache here? There is no need to cache.
What I understand from your need is to make the box on top behaves the same as
the filters.

> 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.

I don't see any other.
We only have the lists and the checkouts using DT + Ajax

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


More information about the Koha-bugs mailing list