Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Rebased WIP: Infrastructure: sceNetInet and sceNetResolver support #19807

Merged
merged 9 commits into from
Jan 4, 2025

Conversation

hrydgard
Copy link
Owner

@hrydgard hrydgard commented Jan 4, 2025

This is #18578 by @JustAWhiteBloodCell, but rebased on the latest codebase.

No clue if it works, but figure it might be a good idea to get it in, as the way it currently is, nobody can work on it. See the other issue for more reasoning about which infrastructure PR to merge.

@hrydgard hrydgard merged commit 5a328a8 into master Jan 4, 2025
19 checks passed
@hrydgard hrydgard deleted the infra-master branch January 4, 2025 20:20
@hrydgard hrydgard mentioned this pull request Jan 4, 2025
@Linblow
Copy link
Contributor

Linblow commented Jan 7, 2025

The way I see it the whole network infrastructure code should be done using the (standalone) Asio C++ library as the network backend. It's robust, well known, and supports lots of platforms, so we wouldn't need to write platform-dependent code. It's also worth noting the current C++ networking technical specification is based on the Asio C++ networking library.

@hrydgard
Copy link
Owner Author

hrydgard commented Jan 7, 2025

That might indeed be a good idea. However I'm not very good at networking and I've never used asio, so switching over isn't gonna be the first priority.

But, none of the changes I'm planning to make is likely to make it harder to switch either.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants