Hi,
You probably already have nginx or apache that can redirect requests to
the proper backend. Why do you need Koha to do that ?
Le 09/07/2020 à 13:49, dc...@prosentient.com.au a écrit :
Hi all,
I was chatting with lmstrand on IRC, and we both came up with separate
features where we’d essentially want Koha to proxy our HTTP requests to
the Koha API endpoint to a backend service running on the Koha server.
What do people think about using the Koha HTTP API that way?
Or would it just make more sense to run up Kong (or another API gateway)
on the Koha server, and use it to proxy HTTP requests to backend
services running on the Koha server? I think in both our cases Koha is
itself only tangentially related. (lmstrand’s is a SIP2 client daemon
available over HTTPS, while mine is a OAI-PMH harvester daemon available
over HTTPS)
The advantage of using the Koha API is that it keeps everything
together. The disadvantage is that we might not want to use Koha to
proxy requests?
The advantage of Kong is that it keeps a separation of concerns, Kong
has a tonne of plugins that make working with APIs a great experience.
The disadvantage is that it’s yet another dependency.
David Cook
Systems Librarian
Prosentient Systems
72/330 Wattle St
Ultimo, NSW 2007
Australia
Office: 02 9212 0899
Online: 02 8005 0595
_______________________________________________
Koha-devel mailing list
Koha-devel@lists.koha-community.org
https://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel
website : http://www.koha-community.org/
git : http://git.koha-community.org/
bugs : http://bugs.koha-community.org/
--
Julian Maurice
BibLibre
_______________________________________________
Koha-devel mailing list
Koha-devel@lists.koha-community.org
https://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel
website : http://www.koha-community.org/
git : http://git.koha-community.org/
bugs : http://bugs.koha-community.org/
