Skip to content
New issue

Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? # to your account

Override response handlers #13

Open
cflipse opened this issue Feb 10, 2016 · 2 comments
Open

Override response handlers #13

cflipse opened this issue Feb 10, 2016 · 2 comments

Comments

@cflipse
Copy link
Contributor

cflipse commented Feb 10, 2016

different HTTP methods are going to have different needs from their response handlers; it should be easy to select a separate response handler to use, so that the same call method doesn't have to handle both DELETE and GET responses.

@cflipse cflipse added this to the v0.5 milestone Jul 27, 2016
@solnic
Copy link
Member

solnic commented Apr 28, 2019

@cflipse is this still needed?

@solnic solnic removed this from the v0.7 milestone Apr 28, 2019
@AMHOL
Copy link
Member

AMHOL commented Apr 28, 2019

@solnic I don't think this is needed, I had a similar case when developing a PoC a few years back and just handed off to another class based on the verb in my adapters request/response handlers, this also allows you to do any processing that is common to all requests before handing off to dependencies.

# for free to join this conversation on GitHub. Already have an account? # to comment
Projects
None yet
Development

No branches or pull requests

3 participants