glassfishrobot

@glassfishrobot Commented @pavelbucek said: the "restriction" is from the JSR 356 itself - as I already mentioned, we cannot guarantee in-order message delivery otherwise. Client/Server side does not matter, since...

@glassfishrobot Commented This issue was imported from java.net JIRA TYRUS-404

* **Issue Imported From:** https://github.com/tyrus-project/tyrus/issues/573 * **Original Issue Raised By:**@glassfishrobot * **Original Issue Assigned To:** @pavelbucek

@glassfishrobot Commented Reported by @pavelbucek

@glassfishrobot Commented @pavelbucek said: there is no good solution for that issue, if we limit the change only to WebSocket API implementation; all we can do here is to introduce...

@glassfishrobot Commented Issue-Links: is related to [WEBSOCKET_SPEC-235](https://github.com/tyrus-project/websocket_spec/issues/412)

@glassfishrobot Commented This issue was imported from java.net JIRA TYRUS-396

* **Issue Imported From:** https://github.com/tyrus-project/tyrus/issues/566 * **Original Issue Raised By:**@glassfishrobot * **Original Issue Assigned To:** @pavelbucek

@glassfishrobot Commented Reported by isart

@glassfishrobot Commented isart said: Currently SSLEngine can be influenced by setting appropriated System properties: System.setProperty(SslContextConfigurator.KEY_STORE_FILE, keystorePath); System.setProperty(SslContextConfigurator.KEY_STORE_PASSWORD, keystorePassword); ... However, using JVM global properties may not be appropriated in several...