<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"><html><head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8"></head><body>A new request with request id 6959 has been created by koha-devel-request@lists.koha-community.org. Short info on the request is : <br><br>Title : Koha-devel Digest, Vol 205, Issue 11<br>Category : <br>Description : <div>Send Koha-devel mailing list submissions to<br> koha-devel@lists.koha-community.org<br><br>To subscribe or unsubscribe via the World Wide Web, visit<br> https://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel<br>or, via email, send a message with subject or body 'help' to<br> koha-devel-request@lists.koha-community.org<br><br>You can reach the person managing the list at<br> koha-devel-owner@lists.koha-community.org<br><br>When replying, please edit your Subject line so it is more specific<br>than "Re: Contents of Koha-devel digest..."<br><br><br>Today's Topics:<br><br> 1. Re: Fundamental flaw in Koha REST API (David Cook)<br> 2. Re: Fundamental flaw in Koha REST API (David Cook)<br> 3. Maximum execution time for background jobs? (David Cook)<br><br><br>----------------------------------------------------------------------<br><br>Message: 1<br>Date: Tue, 6 Dec 2022 11:30:46 +1100<br>From: "David Cook" <dcook@prosentient.com.au><br>To: "'Tomas Cohen Arazi'" <tomascohen@gmail.com>, "'Galen Charlton'"<br> <gmc@equinoxoli.org><br>Cc: "'koha-devel'" <koha-devel@lists.koha-community.org><br>Subject: Re: [Koha-devel] Fundamental flaw in Koha REST API<br>Message-ID: <082501d9090a$00e0b670$02a22350$@prosentient.com.au><br>Content-Type: text/plain; charset="utf-8"<br><br>Perhaps Bug 30165 allowing multiple “q” parameters would provide an alternative as well?<br><br> <br><br>In the DataTables, it looks like it’s used for receiving acquisitions and something with POS registers. <br><br> <br><br>In master, the acquisitions issue is solved by turning off that option switch. (Although in older versions of Koha the Orders route doesn’t seem able to handle the UTF-8 encoded characters.) <br><br> <br><br>David Cook<br><br>Senior Software Engineer<br><br>Prosentient Systems<br><br>Suite 7.03<br><br>6a Glen St<br><br>Milsons Point NSW 2061<br><br>Australia<br><br> <br><br>Office: 02 9212 0899<br><br>Online: 02 8005 0595<br><br> <br><br>From: Tomas Cohen Arazi <tomascohen@gmail.com> <br>Sent: Tuesday, 6 December 2022 11:24 AM<br>To: Galen Charlton <gmc@equinoxoli.org><br>Cc: David Cook <dcook@prosentient.com.au>; koha-devel <koha-devel@lists.koha-community.org><br>Subject: Re: [Koha-devel] Fundamental flaw in Koha REST API<br><br> <br><br>I recall we used the header at some point, to keep the base query clean when adding new filters.<br><br> <br><br>The only alternative is forcing the use of some form of ascii encoding (base64?) But I agree we should better deprecate it.<br><br> <br><br>It's use in the codebase on DT is tied to an option switch and probably not used <br><br> <br><br> <br><br> <br><br>El lun, 5 dic 2022 20:08, Galen Charlton <gmc@equinoxoli.org <mailto:gmc@equinoxoli.org> > escribió:<br><br>Hi,<br><br>On Mon, Dec 5, 2022 at 5:40 PM David Cook <dcook@prosentient.com.au <mailto:dcook@prosentient.com.au> > wrote:<br>> At the moment, it’s not widely used by Koha itself, so I don’t think<br>> it will be hard to remove from Koha, but any third-party integrations<br>> would need to refactor to use a different option.<br><br>This might not be a huge factor, though of course removing that header<br>should go through a deprecation procedure.<br><br>Specifically, upon skimming the results of a GitHub search of<br>"x-koha-query", the only uses I found outside of Koha itself were in<br>plugins published by a couple active community members.<br><br>Regards,<br><br>Galen<br>-- <br>Galen Charlton<br>Implementation and IT Manager<br>Equinox Open Library Initiative<br>gmc@equinoxOLI.org <mailto:gmc@equinoxOLI.org> <br>https://www.equinoxOLI.org<br>phone: 877-OPEN-ILS (673-6457)<br>direct: 770-709-5581<br>_______________________________________________<br>Koha-devel mailing list<br>Koha-devel@lists.koha-community.org <mailto:Koha-devel@lists.koha-community.org> <br>https://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel<br>website : https://www.koha-community.org/<br>git : https://git.koha-community.org/<br>bugs : https://bugs.koha-community.org/<br><br>-------------- next part --------------<br>An HTML attachment was scrubbed...<br>URL: <http://lists.koha-community.org/pipermail/koha-devel/attachments/20221206/2f29dce5/attachment-0001.htm><br><br>------------------------------<br><br>Message: 2<br>Date: Tue, 6 Dec 2022 11:33:03 +1100<br>From: "David Cook" <dcook@prosentient.com.au><br>To: "'Tomas Cohen Arazi'" <tomascohen@gmail.com>, "'Galen Charlton'"<br> <gmc@equinoxoli.org><br>Cc: "'koha-devel'" <koha-devel@lists.koha-community.org><br>Subject: Re: [Koha-devel] Fundamental flaw in Koha REST API<br>Message-ID: <082a01d9090a$4d79a140$e86ce3c0$@prosentient.com.au><br>Content-Type: text/plain; charset="utf-8"<br><br>Btw looks like Bug 30165 is what resolves the UTF-8 issue for the orders route…<br><br> <br><br>David Cook<br><br>Senior Software Engineer<br><br>Prosentient Systems<br><br>Suite 7.03<br><br>6a Glen St<br><br>Milsons Point NSW 2061<br><br>Australia<br><br> <br><br>Office: 02 9212 0899<br><br>Online: 02 8005 0595<br><br> <br><br>From: David Cook <dcook@prosentient.com.au> <br>Sent: Tuesday, 6 December 2022 11:31 AM<br>To: 'Tomas Cohen Arazi' <tomascohen@gmail.com>; 'Galen Charlton' <gmc@equinoxoli.org><br>Cc: 'koha-devel' <koha-devel@lists.koha-community.org><br>Subject: RE: [Koha-devel] Fundamental flaw in Koha REST API<br><br> <br><br>Perhaps Bug 30165 allowing multiple “q” parameters would provide an alternative as well?<br><br> <br><br>In the DataTables, it looks like it’s used for receiving acquisitions and something with POS registers. <br><br> <br><br>In master, the acquisitions issue is solved by turning off that option switch. (Although in older versions of Koha the Orders route doesn’t seem able to handle the UTF-8 encoded characters.) <br><br> <br><br>David Cook<br><br>Senior Software Engineer<br><br>Prosentient Systems<br><br>Suite 7.03<br><br>6a Glen St<br><br>Milsons Point NSW 2061<br><br>Australia<br><br> <br><br>Office: 02 9212 0899<br><br>Online: 02 8005 0595<br><br> <br><br>From: Tomas Cohen Arazi <tomascohen@gmail.com <mailto:tomascohen@gmail.com> > <br>Sent: Tuesday, 6 December 2022 11:24 AM<br>To: Galen Charlton <gmc@equinoxoli.org <mailto:gmc@equinoxoli.org> ><br>Cc: David Cook <dcook@prosentient.com.au <mailto:dcook@prosentient.com.au> >; koha-devel <koha-devel@lists.koha-community.org <mailto:koha-devel@lists.koha-community.org> ><br>Subject: Re: [Koha-devel] Fundamental flaw in Koha REST API<br><br> <br><br>I recall we used the header at some point, to keep the base query clean when adding new filters.<br><br> <br><br>The only alternative is forcing the use of some form of ascii encoding (base64?) But I agree we should better deprecate it.<br><br> <br><br>It's use in the codebase on DT is tied to an option switch and probably not used <br><br> <br><br> <br><br> <br><br>El lun, 5 dic 2022 20:08, Galen Charlton <gmc@equinoxoli.org <mailto:gmc@equinoxoli.org> > escribió:<br><br>Hi,<br><br>On Mon, Dec 5, 2022 at 5:40 PM David Cook <dcook@prosentient.com.au <mailto:dcook@prosentient.com.au> > wrote:<br>> At the moment, it’s not widely used by Koha itself, so I don’t think<br>> it will be hard to remove from Koha, but any third-party integrations<br>> would need to refactor to use a different option.<br><br>This might not be a huge factor, though of course removing that header<br>should go through a deprecation procedure.<br><br>Specifically, upon skimming the results of a GitHub search of<br>"x-koha-query", the only uses I found outside of Koha itself were in<br>plugins published by a couple active community members.<br><br>Regards,<br><br>Galen<br>-- <br>Galen Charlton<br>Implementation and IT Manager<br>Equinox Open Library Initiative<br>gmc@equinoxOLI.org <mailto:gmc@equinoxOLI.org> <br>https://www.equinoxOLI.org<br>phone: 877-OPEN-ILS (673-6457)<br>direct: 770-709-5581<br>_______________________________________________<br>Koha-devel mailing list<br>Koha-devel@lists.koha-community.org <mailto:Koha-devel@lists.koha-community.org> <br>https://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel<br>website : https://www.koha-community.org/<br>git : https://git.koha-community.org/<br>bugs : https://bugs.koha-community.org/<br><br>-------------- next part --------------<br>An HTML attachment was scrubbed...<br>URL: <http://lists.koha-community.org/pipermail/koha-devel/attachments/20221206/59d9e5f6/attachment-0001.htm><br><br>------------------------------<br><br>Message: 3<br>Date: Tue, 6 Dec 2022 12:27:58 +1100<br>From: "David Cook" <dcook@prosentient.com.au><br>To: "'koha-devel'" <koha-devel@lists.koha-community.org><br>Subject: [Koha-devel] Maximum execution time for background jobs?<br>Message-ID: <083d01d90911$faa6cdf0$eff469d0$@prosentient.com.au><br>Content-Type: text/plain; charset="utf-8"<br><br>Hi all,<br><br> <br><br>I was closing old Bugzilla bugs when I bumped into "Bug 10460 - way to stop<br>a run away report".<br><br> <br><br>It got me thinking about maximum execution time for background jobs. What do<br>people think about background jobs workers killing their child processes if<br>they exceed a maximum execution time?<br><br> <br><br>I don't have a particular use case for it at the moment, so not a priority<br>by any means, but thoughts on the concept?<br><br> <br><br>David Cook<br><br>Senior Software Engineer<br><br>Prosentient Systems<br><br>Suite 7.03<br><br>6a Glen St<br><br>Milsons Point NSW 2061<br><br>Australia<br><br> <br><br>Office: 02 9212 0899<br><br>Online: 02 8005 0595<br><br> <br><br>-------------- next part --------------<br>An HTML attachment was scrubbed...<br>URL: <http://lists.koha-community.org/pipermail/koha-devel/attachments/20221206/34ab783f/attachment.htm><br><br>------------------------------<br><br>Subject: Digest Footer<br><br>_______________________________________________<br>Koha-devel mailing list<br>Koha-devel@lists.koha-community.org<br>https://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel<br>website : https://www.koha-community.org/<br>git : https://git.koha-community.org/<br>bugs : https://bugs.koha-community.org/<br><br><br>------------------------------<br><br>End of Koha-devel Digest, Vol 205, Issue 11<br>*******************************************<br></div><br><br>NOTE: You are receiving this mail because, the Requester/Technician wanted you to get notified on this request creation.<br></body></html>