Multiple BSD connections

1+2+3) This is really something you need decide for yourself and what fits best your application needs. The BSD socket implementation is thread-safe for the most relevant part. As things can be used in non-blocking mode, it could work in a single thread and polling all sockets, or multi-threaded, using blocking calls on each socket.

5) And as the BSD sockets use the native TCP and UDP sockets underneath, the same memory management is used in this regard.

1+2+3) This is really something you need decide for yourself and what fits best your application needs. The BSD socket implementation is thread-safe for the most relevant part. As things can be used in non-blocking mode, it could work in a single thread and polling all sockets, or multi-threaded, using blocking calls on each socket.

5) And as the BSD sockets use the native TCP and UDP sockets underneath, the same memory management is used in this regard.

Dear Andreas Barth,

Thank you so much for your response! I truly appreciate your help. I have a couple of questions that I hope you can assist me with:

1. When I define two threads consecutively with the same priority, only the one thread seems to run continuously, even when using a round-robin scheduling method. Do you have any suggestions on how I can resolve this issue?

  osThreadCreate (osThread(Server), (void *)SOCK_STREAM);
  osThreadCreate (osThread(Server), (void *)SOCK_STREAM);

  while(1) {
    osSignalWait (0, osWaitForever);
  }

1. Regarding the listen(sock, 1) command, should the second argument remain as 1 when using different server threads? I'm concerned that it may not be able to handle multiple socket connections in blocking mode.
2. could you provide an example of how to use ioctlsocket? There is no additional information about how to handle the "accept" function after non-blocking listen function.
3. Are there any examples of implementing multiple BSD connections using the listen function?

Thank you again for your assistance.

Dear Andreas Barth,

I followed various steps, but the documentation on BSD is full of flaws, which has left me feeling confused. Is there an example of multiple BSD connections in MDK? 

My code

			 sd = socket (addr.sin_family, type, 0);
			 sck_mode = 1;	
			 ioctlsocket (sd , FIONBIO, &sck_mode);
			 bind (sd, (SOCKADDR *)&addr, sizeof(addr));
			 listen (sd, 4);

The code above does not open more than one connection.

-------------

Some of the flaws:

https://www.keil.com/pack/doc/mw6/Network/html/group__bsd__routines.html#gac6b00a29e8f1664d7ba4a70bfb92d9db

In the sample code, the addr is a member of SOCKADDR_IN, which can't be sent to SOCKADDR (the fourth item in the recvfrom command).

https://www.keil.com/pack/doc/mw6/Network/html/group__bsd__routines.html#ga0b42eb9e32b55aff7130ef48afd8b885

In the sample code, SCK_SUCCESS is not defined. The correct term is BSD_SUCCESS.

In addition, I would like to understand how to determine when a request is sent to a non-blocking listener so that I can accept it using the accept command.

Hi,

I would like to provide some clarification regarding my questions:

1. Listen Command: The second argument in the listen(sock, 1) command should correspond to the number of connections you wish to allow.
2. Non-Blocking Commands: I utilize the ioctlsocket function to convert certain blocking commands into non-blocking ones.
3. Documentation Improvements: I recommend addressing these issues in the documentation for better clarity and guidance.

https://www.keil.com/pack/doc/mw6/Network/html/group__bsd__routines.html#gac6b00a29e8f1664d7ba4a70bfb92d9db

In the sample code, the addr is a member of SOCKADDR_IN, which can't be sent to SOCKADDR (the fourth item in the recvfrom command).

https://www.keil.com/pack/doc/mw6/Network/html/group__bsd__routines.html#ga0b42eb9e32b55aff7130ef48afd8b885

In the sample code, SCK_SUCCESS is not defined. The correct term is BSD_SUCCESS.

The MDK version 6 middleware you mentioned is outdated and is no longer being developed. It was abandoned almost 10 years ago. You can find the current MDK middleware documentation here.