Summary: | Set a timeout to z3950 servers that could have network problems occasionally | ||
---|---|---|---|
Product: | Koha | Reporter: | Juan Romay Sieira <juan.sieira> |
Component: | Z39.50 / SRU / OpenSearch Servers | Assignee: | Juan Romay Sieira <juan.sieira> |
Status: | CLOSED FIXED | QA Contact: | Bugs List <koha-bugs> |
Severity: | enhancement | ||
Priority: | P5 - low | CC: | henridamien.laurent, jcamins, paul.poulain |
Version: | 3.8 | ||
Hardware: | All | ||
OS: | All | ||
GIT URL: | Change sponsored?: | --- | |
Patch complexity: | --- | Documentation contact: | |
Documentation submission: | Text to go in the release notes: | ||
Version(s) released in: | Circulation function: | ||
Attachments: |
pro
Patch to apply in current master Patch to apply in current master patch signed off |
Description
Juan Romay Sieira
2011-04-08 10:24:41 UTC
Comment hidden (obsolete)
Created attachment 7615 [details] [review] Patch to apply in current master Is the timeout setting in seconds? I would suggest adding that information to the Z39.50 server entry form. I recommend this: Timeout (Enter 0 for no timeout): [ ] seconds I would also like to see a message displayed on the search results screen about which servers were skipped because of a timeout. There's already error output for "actual" timeouts, so it's logical to include these "voluntary" timeouts too. Created attachment 8414 [details] [review] Patch to apply in current master I've done some changes that Owen commented. Information in seconds when edit a z3950 server and inform if a server has timeout or connection failed errors. Created attachment 8453 [details] [review] patch signed off QA comment: * code very clean * add an interesting fallback in case of timeout * could not test a timeout case, but everything still works if the z3950 server is responsive enough. * the "timeout" error message is displayed in case of timeout (at least reading the code) passed QA There have been no further reports of problems so I am marking this bug resolved. |