Currently, patron images are not cached and it takes a considerable amount of time to retrieve it in the staff client. To reproduce: - Go to a patron's detail page (choose a patron with an image attached) - Enable the browser's network profiling interface - Switch between tabs (Checkouts, Details, Fines, etc) => FAIL: patronimage.pl&borrowernumber=X is retrieved each time [1] I've been told it is intended that each time the patron image is updated it has to instantly load the new one. This could be better handled using a timestamp and the Last-Modified header. [1] In my dev box it took it 1'' to load the single image.
I imagine an Etag header using a MD5 hash of the patron image would work well