https://bz.apache.org/bugzilla/show_bug.cgi?id=60597
--- Comment #5 from Michael Orr <michaelomich...@gmail.com> --- Hi Christopher, Thanks for the feedback. I'm just following the example set by other configuration entities in this area (e.g. the SSL_PROTOCOLS property). In general I'd much prefer the direct mutators approach as well. In this case, however, the intent is to provide additional configuration capabilities to the generic javax.websocket.* API classes that were missing from that generic API. The choice for a user would be either to use these properties or to abandon the javax.websocket.* classes and instead use Tomcat-specific implementations of them (e.g. org.apache.tomcat.websocket.WsWebSocketContainer). The latter would make the user's code much less portable overall, so I think that using properties here and sticking to the javax interfaces is the better approach. Of course, the best thing would be if protocol/ciphers configurability were to be added to the official java.websocket.* API spec, but I have no idea when that's coming... Michael -- You are receiving this mail because: You are the assignee for the bug. --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org For additional commands, e-mail: dev-h...@tomcat.apache.org
