-
Notifications
You must be signed in to change notification settings - Fork 7
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Support of the Rest API #4
Comments
I think we should rename the old class to the SoapAPI, create the new one to RestAPI and use Delegation via the API class which could decide then how to route the requests. |
And who would make the decision? |
Yep, it should be a parametric call. |
What do you mean by that? |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I would like to how the rest api should be included.
Should there be a configuration where you can choose what endpoint (soap or rest) the gem should use?
Or should there be a check if one endpoint is not responding as expected try the other one?
The text was updated successfully, but these errors were encountered: