Skip to content
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

Open
janz93 opened this issue Apr 23, 2017 · 4 comments
Open

Support of the Rest API #4

janz93 opened this issue Apr 23, 2017 · 4 comments

Comments

@janz93
Copy link
Collaborator

janz93 commented Apr 23, 2017

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?

@arbox
Copy link
Owner

arbox commented Apr 23, 2017

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.

@janz93
Copy link
Collaborator Author

janz93 commented Apr 23, 2017

And who would make the decision?
Is that up for the user of the gem?

@arbox
Copy link
Owner

arbox commented Apr 23, 2017

Yep, it should be a parametric call.

@janz93
Copy link
Collaborator Author

janz93 commented Apr 23, 2017

What do you mean by that?
Could you rephrase that?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants