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

Interception chains should be also usable for web sockets #49

Open
cescoffier opened this issue Dec 10, 2013 · 4 comments
Open

Interception chains should be also usable for web sockets #49

cescoffier opened this issue Dec 10, 2013 · 4 comments
Labels

Comments

@cescoffier
Copy link
Member

The interceptors class might be a bit different.

@cescoffier
Copy link
Member Author

Actually it would be filters, not interceptors

@cescoffier cescoffier added this to the 0.5 milestone Apr 5, 2014
@cescoffier cescoffier modified the milestones: 0.6, 0.5 Apr 30, 2014
@cescoffier
Copy link
Member Author

I've started working on it, but it's rather complex as we need to intercept inbound and outbound events. So postponed the issue to the next release.

@cescoffier cescoffier modified the milestones: 0.7, 0.6 Jun 23, 2014
@remi-parain
Copy link
Contributor

Will this issue fixed for 0.7 ?
It would be very handy to have a common way to filter the inbounds (REST/WS ).

@cescoffier
Copy link
Member Author

I would like to have this feature in 0.7 too, but it’s really tricky, and the internal event model needs to be completely redesigned. So unfortunately, it might be delayed again (not sure yet). 

On 15 juillet 2014 at 15:31:13, PARAIN Rémi ([email protected]) wrote:

Will this issue fixed for 0.7 ?
It would be very handy to have a common way to filter the inbounds (REST/WS ).


Reply to this email directly or view it on GitHub.

@cescoffier cescoffier modified the milestone: 0.7 Dec 26, 2014
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants