Hello,
not really sure if this will lead to something, but I just want to have a small discussion about the Berkley Sockets API.
Recently i've been working on TCP Client/Server architectures, and while these lovely Sockets do the things they're supposed to do, I often find myself struggling with the API or inner workings of the Sockets.
An example is when I establish a connection on a local port to a remote port. When the connection is established, there's a point in time where I need to either re-establish the connection or connect to a different system from the same port. More often then not I have to wait a long time for the socket component to be fully destroyed by the system before I can rebind the socket on the port. Event when the application is terminated.
I'm aware this is rather a Kernel/OS issue and not really the Berkley Socket API fault, but there's more of these little things that strike me when working with it.
Anyone else have these quircks with the API?
not really sure if this will lead to something, but I just want to have a small discussion about the Berkley Sockets API.
Recently i've been working on TCP Client/Server architectures, and while these lovely Sockets do the things they're supposed to do, I often find myself struggling with the API or inner workings of the Sockets.
An example is when I establish a connection on a local port to a remote port. When the connection is established, there's a point in time where I need to either re-establish the connection or connect to a different system from the same port. More often then not I have to wait a long time for the socket component to be fully destroyed by the system before I can rebind the socket on the port. Event when the application is terminated.
I'm aware this is rather a Kernel/OS issue and not really the Berkley Socket API fault, but there's more of these little things that strike me when working with it.
Anyone else have these quircks with the API?