James, this does not make any sense to me. Last I heard browsers no longer run java. Why would JSE give a hang about designing a communications mechanism for browsers on the client side? That is the job of the browser developers. On the other hand, JSE WebSocket is the best thing to come along for java clients since RMI which was released I think in 1.1. Java WebSocket is NOT for browsers....it's for Java clients!!!! 😊 And I'm quite pleased with the progress I've made refactoring to use the jdk9 WebSocket api together with wildfly11 on the server (and still blazingly FAST -- seems to be snappier than jdk8 implementation). Now if the IDEs would get in gear to fully implement jdk9 I'd be in fat city.
And my thanks to everyone who has participated in this particular conversation on this list and all the expertise that has been shared. >Yes, there's no formal definition of high/low level, but in the case of WebSockets, we can draw some lines based roughly on what web browsers (which is the target application developer experience that >WebSockets were designed for) support as being high level, and what the WebSocket protocol allows beyond this as low level. > > Regards, > > James > >
