xiaotailang commented on issue #10932:
URL: https://github.com/apache/nuttx/issues/10932#issuecomment-1771947264
Okay, thank you very much
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the spec
xiaoxiang781216 commented on issue #10932:
URL: https://github.com/apache/nuttx/issues/10932#issuecomment-1770412903
There are many solution here:
1. one thread per connection
2. one thread + poll/select
3. libuv
--
This is an automated message from the Apache Git Service.
To
xiaotailang commented on issue #10932:
URL: https://github.com/apache/nuttx/issues/10932#issuecomment-1770406112
Thank you very much for your previous response. After opening tcpbacklog, I
was able to listen to connections normally. I have studied that, by default,
the maximum number of con
xiaotailang commented on issue #10932:
URL: https://github.com/apache/nuttx/issues/10932#issuecomment-1767470901
Thank you very much for your kind assistance. Upon a further review, I found
that if the CONFIG_NET_TCPBACKLOG is enabled, the corresponding logic is to
first select and then acc
xiaoxiang781216 commented on issue #10932:
URL: https://github.com/apache/nuttx/issues/10932#issuecomment-1766125927
it's a very minor implementation issue, I don't believe that the spec
defines the behavior in this particular case. So, I would suggest to follow
other OS's behavior to make
pkarashchenko commented on issue #10932:
URL: https://github.com/apache/nuttx/issues/10932#issuecomment-1765957496
Do you have `CONFIG_NET_TCPBACKLOG` enabled in your test?
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and u
xiaotailang opened a new issue, #10932:
URL: https://github.com/apache/nuttx/issues/10932
Hello everyone, I have noticed an issue while using socket for multiplexing.
I wrote a server program based on non-blocking sockets and select. However,
when I tried to connect to the server using a te
