https://bz.apache.org/bugzilla/show_bug.cgi?id=64644
--- Comment #5 from Saksham Verma <saksham.ve...@gmail.com> --- As per your suggestion(In reply to Mark Thomas from comment #4) > This issue describes one particular drawback of the max idle timeout feature > of WebSocket sessions in the Java WebSocket spec. > > I've been thinking about various WebSocket usage patterns and whether there > was a way to add a custom option that changed how this was treated. E.g. > only applied to reads, only applied to writes, etc.). My conclusion is that > to cover all possible use cases you need three idle timeouts: > - maxIdleTimeout (the current value) > - maxIdleReadTimeout > - maxIdleWriteTimeout > > This is probably something that needs to be added to the Jakarta WebSocket > 2.1 spec. I've created > https://github.com/eclipse-ee4j/websocket-api/issues/356 to track this > > To address this in current Tomcat versions, I am thinking of a couple of > custom properties in the user properties Map associated with the session. As per this suggestion I have raised another PR https://github.com/apache/tomcat/pull/346 including the supporting tests. Could you please review it? We need to deploy this fix for our product Thingworx as it is impacting many of our customers. -- 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
