Skip to content

Conversation

@Yacubane
Copy link
Contributor

Within #501 WEBSOCKETS_TCP_TIMEOUT was changed to 5 seconds, which is a very large number, especially when dealing with a lot of clients inside local network environment. #501 was marked as solution for #441 but I don't believe that it's proper way to deal with this problem. There should be possibility to change this parameter, which is mentioned in #661.

This PR wraps WEBSOCKETS_TCP_TIMEOUT inside #ifndef to allow defining this variable for custom setup.

There is still room for improvement, like @adamczuk-piotr proposed, there could be two different timeout variables, one responsible for connecting, and another one for reading. Having one for writing data would be great as well. I can implement it but I would like to get feedback from author if it makes sense.

@Links2004 Links2004 merged commit 323592f into Links2004:master Aug 22, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

2 participants