Installation of EventBusBridgeHook missing within SockJSHandlerImpl about vertx-web HOT 6 CLOSED

I was thinking of removing the eventbusbridgehook. Can you explain your use case and why it is useful to you?

from vertx-web.

I am still within the design phase of my project, but here are some ideas I thought could be implemented by a hook:
a) Check the country of the client and reject them based on a ip->country mapping service
b) Prevent too many requests of a client within a time-frame by counting requests by sessionId (apexSession?)
c) Collect some statistics about the client browser agent

from vertx-web.

I think all of those should be doable using standard Apex handlers?

from vertx-web.

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.

from vertx-web.

OK, let me know how it goes :)

from vertx-web.

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.

from vertx-web.