Hi Dieter,
The current WebSocket implementation is based on Jetty’s WebSocket API. This was clearly missing in the documentation (thanks for the pointer), so I have just updated our Wiki pages [1].
It appears that Jetty’s implementation of the official JSR-356 WebSocket API is pretty stable nowadays. As it’s quite similar to their custom API (which served as inspiration for the generic API), we might switch to the new version in future versions of BaseX.
All the best, Christian
[1] http://docs.basex.org/wiki/WebSockets
On Mon, Oct 22, 2018 at 6:34 AM Dieter Zanzinger dieter.zanzinger@icloud.com wrote:
Hi, BaseX-Team,
I tested the new websocket-feature. The .zip- installation on Win10 (your embedded jetty) worked (your chat-app). But I had problems with the .war -installation on tomcat. With the standard-installation, the paths in the chat.js had to be preceded with /BaseX - ok so far. I get the login-page and main-page visible - ok. But when the main-page is loading, the network call to http://localhost:8080/BaseX/ws/chat fails with http-code 404. I think, there is a problem with paths as well?
It would be great, if you could add documentation for Tomcat as well.
Thanks for this great tool!
Dieter Zanzinger