-
Notifications
You must be signed in to change notification settings - Fork 530
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
Installation of EventBusBridgeHook missing within SockJSHandlerImpl #71
Comments
I was thinking of removing the eventbusbridgehook. Can you explain your use case and why it is useful to you? |
I am still within the design phase of my project, but here are some ideas I thought could be implemented by a hook: |
I think all of those should be doable using standard Apex handlers? |
Yes, you are right. The RoutingContext has everything inside which is need for implementing that. Today I discovered "routingContext.next()" in the apex docs. It seems that apex handles can be chained this way? Anyway, I do agree removing the hook. |
OK, let me know how it goes :) |
Well, I can't use standard Apex handlers to count incoming websocket frames. The standard handlers will not be invoked for websocket communication happening after the protocol upgrade. What I need is some interceptor that gets invoked on every incoming frame. |
At SockJSHandlerImpl line 92 the EventBusBridgeHook does not get installed into the EventBusBridgeImpl, so the hook within SockJSHandlerImpl is useless.
Solution: Either call the method EventBusBrodgeImpl.setHook(this.hook) or create another constructor for the EventBusBridgeImpl and pass it to the constructor when creating the instance.
The text was updated successfully, but these errors were encountered: