Hi Andy, I wanted to introduce new options first, but I dropped this approach, and I decided to simulate the old behavior of Jetty. The init-param entries in the web.xml file are now parsed by BaseX and assigned to the WebSocket instance when the first WebSocket connection is created [1].
As a consequence, existing Jetty 9 web.xml WebSocket configurations should work again. Feel free to check out the latest snapshot [2] to verify if that’s true. Best, Christian PS: The docs have been updated, too [3]. [1] https://github.com/BaseXdb/basex/commit/880535ed23d11c15b58945d12049242af65486f1 [2] https://files.basex.org/releases/latest/ [3] https://docs.basex.org/main/WebSockets#configuration ________________________________ Von: Andy Bunce <bunce.a...@gmail.com> Gesendet: Montag, 4. August 2025 00:39 An: BaseX <basex-talk@mailman.uni-konstanz.de> Betreff: [basex-talk] Websocket configuration Basex 12 Hi, I would like to increase the websocket message length from the default of 64 KB. The websocket documentation implies this can be done via web.xml [1] However, while searching for the syntax I came across the suggestion it is different with the Jetty version 12 API [2] The Jetty docs have this example [3] // Configure the ServerContainer. container.setDefaultMaxTextMessageBufferSize(128 * 1024); but my quick code search of the BaseX source found nothing similar. Is it possible to configure the webSocket MaxTextMessageBufferSize in BaseX 12.0? /Andy [1] https://docs.basex.org/main/WebSockets#configuration [2] https://stackoverflow.com/questions/79610426/setting-the-max-buffer-size-for-websocketclient-since-upgrading-to-jetty-12 [3] https://jetty.org/docs/jetty/12/programming-guide/server/websocket.html#standard-endpoints
