-
Notifications
You must be signed in to change notification settings - Fork 129
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
Comments
To be honest, I completely missed this in ring. I will catch up with current ring and check whether this is possible. |
It's not a major feature, but something the ring team did to help out the Pedestal project: http://pedestal.io/documentation/service-interceptors/ |
I see, I just wanted to ask about where to find more information. |
Is this done ? I would like to use liberator with pedestal services. |
@murtaza52 as far as I understand, regular ring handlers like those liberator creates can be server from pedestal. |
Is there an example of this as of today ? Some guidelines to get started integrating pedestal and liberator ? |
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?
The text was updated successfully, but these errors were encountered: