https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=27423
--- Comment #8 from Arthur Suzuki <[email protected]> --- (In reply to David Cook from comment #7) > To play devil's advocate, what's the main reasons for removing the ILS-DI > API? > > Is it due to security issues? Maintainability? Code duplication? > > Personally, I dislike how it's only IP restricted. I would like more robust > authentication. If implementing more robust auth, then client/third-party software will have to adapt their connectors specifically for Koha I'd say, code duplication is a point, some bugs are working on "merging" code back from the interfaces to C4 or Koha namespace. Thinking of bz25408 (which I rebased this night) but there are others pushing in that way. This is also a good opportunity to centralize some controls on sysprefs and circ rules, things which are also beneficial for Staff, Opac and API interfaces. From my point of view, ILS-DI is an opportunity to spot things and have a look on other stuff. > > While I know that third-parties use the ILS-DI API, I don't know the history > there. Did they develop client tools for generic ILS-DI APIs or did they > always develop specifically for Koha's implementation of ILS-DI? Speaking for Bokeh (php) we have an "AbstractILSDIService" class which we extends to any library software using ILS-DI. Small differences in the implementations are handled by overloading specific calls or properties. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug. _______________________________________________ Koha-bugs mailing list [email protected] https://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-bugs website : http://www.koha-community.org/ git : http://git.koha-community.org/ bugs : http://bugs.koha-community.org/
