Open vorburger opened 6 years ago
@edewit @sebastienblanc we also could build this using the Netty rather than the Jetty WebSocket client library? IMHO given that Vert.x uses Netty we not only could but should use it.
Web search of "netty websocket client" brings up various blog posts and third party examples like or this etc. but I'm guessing this core netty example is probably what we want to look at.
@vorburger a Java client on top of the SockJS bridge makes sense (your point about firewall restrictions is spot on). But the goal of this project is to have a Java client with minimal (ideally zero) dependencies.
A separate project would make sense though. As for the tooling, I would focus on OKHttp since it's used a lot by Android developers.
carrying over from #2 : Currently this project uses the Vert.x
TcpEventBusBridge
, whereas I was hoping to find something like this for thatSockJSHandler
... exposing HTTP instead TCP, to make it easy to use the Vert.x Event Bus by Java (not Web JS) clients running outside of a firewall letting only HTTP through, such as when deploying Vert.x on OpenShift.@edewit has pointed to the Jetty WebSocket client is being of possible interest to implement this.