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 new interceptor model that Ring now supports #56

Open
eslick opened this issue Jul 2, 2013 · 6 comments
Open

Support new interceptor model that Ring now supports #56

eslick opened this issue Jul 2, 2013 · 6 comments

Comments

@eslick
Copy link

eslick commented Jul 2, 2013

Ring refactored the standard handlers to support the more complicated, but async-io friendly, interceptor model that separates request handling from response generation. Is liberator friendly to a similar refactoring? If so, is this something you are interested or I might take on in a few months when I need the interceptor model?

@ordnungswidrig
Copy link
Member

To be honest, I completely missed this in ring. I will catch up with current ring and check whether this is possible.

@eslick
Copy link
Author

eslick commented Jul 6, 2013

It's not a major feature, but something the ring team did to help out the Pedestal project: http://pedestal.io/documentation/service-interceptors/

@ordnungswidrig
Copy link
Member

I see, I just wanted to ask about where to find more information.

@murtaza52
Copy link

Is this done ? I would like to use liberator with pedestal services.

@ordnungswidrig
Copy link
Member

@murtaza52 as far as I understand, regular ring handlers like those liberator creates can be server from pedestal.

@nha
Copy link

nha commented Nov 12, 2015

Is there an example of this as of today ? Some guidelines to get started integrating pedestal and liberator ?

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

No branches or pull requests

4 participants