You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In the last change the initialization of the ByteBuffer changed from using the limit (Standard BinaryMessage Constructor using limit) to using the max capacity which leads to a buffer which is filled up with zeros until his capacity is reached (ed172d6#diff-43448f6e16d92d0df476c611919c95839ad9f2874d149cf939d8f91a2824b5f3)
Is there any reason to do that and not changing the mentioned Line 121 to using limit again? In our case that leads to some troubles with protobuf from google which expects that a buffer ends with exact 1 "0"!
Thanks a lot for a discussion in advance!
Best regards,
Martin
The text was updated successfully, but these errors were encountered:
Hi Team,
Short Question from my side regarding
spring-framework/spring-websocket/src/main/java/org/springframework/web/socket/adapter/jetty/JettyWebSocketHandlerAdapter.java
Line 121 in 22bf4df
In the last change the initialization of the ByteBuffer changed from using the limit (Standard BinaryMessage Constructor using limit) to using the max capacity which leads to a buffer which is filled up with zeros until his capacity is reached (ed172d6#diff-43448f6e16d92d0df476c611919c95839ad9f2874d149cf939d8f91a2824b5f3)
Is there any reason to do that and not changing the mentioned Line 121 to using limit again? In our case that leads to some troubles with protobuf from google which expects that a buffer ends with exact 1 "0"!
Thanks a lot for a discussion in advance!
Best regards,
Martin
The text was updated successfully, but these errors were encountered: