We often call a server connect function from a different server connect call, by using the API Action. This works well, and allows us to reuse a complex database query and checks etc. However I’m wondering if there is a better way to do this rather than using the API Action?
The only real problem we have with this approach is it doesn’t seem possible to use localhost in the API call - we have to use either an IP address, or a FQDN. Using localhost throws a security error (even though there is no security on the server connect call to retrieve this data).
Using a fixed address has been ok for testing, and has worked fine over the past few months as we’ve just been running on a development system, however as we move to a production server, having a fixed address doesn’t work as we need to refer to different systems in each case.
It would be fine if we can use localhost, but better if there was a more ‘integrated’ way to call one server connect method from within another and I’d welcome any thoughts others have on achieving this goal.
Last updated: