Skip to content

Conversation

@schellingb
Copy link

Hi

I made some improvements/changes to sts_net and was wondering if you're interested.
It's mostly fixes (build improvements, etc.) and optional additional functions (get the host name or ip of a connected client and enumerate host machine network interfaces), but there's one bigger change.

Commit 47a53d4 changes how sts_net_set_t handles sockets. Instead of having the user code manage an array of sockets itself I thought it would be easier and more useful to have the sockets right in there. This removes the need adding/removing them manually. I added get_available_socket_from_set which returns an available socket and sts_net_drop_socket which can be used instead of accept_socket in case the set is full.

See the updated example of how these changes can be used.

If you're only interested in a subset of these I can prepare a new branch+pull request.

Cheers

schellingb and others added 12 commits April 7, 2017 12:15
…ess) of a connected client (or the listen interface of a server)
- Split sts_net_open_socket into sts_net_listen (server) and sts_net_connect (client)
- Changed socket set to contain sockets not user managed pointer to sockets
- Added sts_net_get_available_socket_from_set which returns a socket for accepting
- Added sts_net_drop_socket which can be used to drop a new connection if no socket is available
- Removed sts_net_add_socket_to_set and sts_net_remove_socket_from_set as it is now automatic!
- Updated example
added want_local_name to sts_net_gethostname
added share_port option to sts_net_listen
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant