So far I understand that posix/ unix and windows systems have their own methods of creating and using socket connections.
Windows sockets use extra steps for setup like WSAStartup for initializing Windows sockets DLL and WSACleanup, the flow is still the same like on Posix. ...
I found this useful source: https://medium.com/@adityakumarbgs6/network-programming-part-1-using-winsock-programming-sockets-1978e4de94a2
How will polyscoket library integrate this decision of what headers to use?
I've been working with Esp Displays and I seen some libraries use preprocessor macros like #ifdef Display1 include Display1Driver ... maybe we can use this here. Is there is a better way to do this? @matas-noreika I think you would know more about this than me. What are your thoughts to going about this library?
So far I understand that posix/ unix and windows systems have their own methods of creating and using socket connections.
Windows sockets use extra steps for setup like WSAStartup for initializing Windows sockets DLL and WSACleanup, the flow is still the same like on Posix. ...
I found this useful source: https://medium.com/@adityakumarbgs6/network-programming-part-1-using-winsock-programming-sockets-1978e4de94a2
How will polyscoket library integrate this decision of what headers to use?
I've been working with Esp Displays and I seen some libraries use preprocessor macros like #ifdef Display1 include Display1Driver ... maybe we can use this here. Is there is a better way to do this? @matas-noreika I think you would know more about this than me. What are your thoughts to going about this library?