Community
Participate
Working Groups
What I want to do is to use a client to connect to some server, but I don't want to use the IP address (x.x.x.x:y) but use the host name as my.server.com:4566. This is platform dependant, that's why I'm opening the bug to discuss how to approach (or even if it's actually necessary). I stumble upon this problem when trying to connect using HTTP to some server, whose ip address wasn't fix, but the hostname was. I know there's a "getaddrinfo" function in posix, but I'm not sure yet how to handle this. I could add this functionality first in the HTTP module with platform dependant code to reduce the effects of it.
This is an issue we know already for quite some time. See also the bug in the old bug tracker [1]. Ingo spent some time on it and it turned out it is not as easy as it seemed in the start. Therefore I think haveing a firs version just for the HTTP could be a good starting point to learn more about it. [1] https://sourceforge.net/p/fordiac/issues/443/
But why put it into the HTTP module? In order to get the correct error responses for Windows and BSD compatible network interfaces, we already introduced platform dependent code blocks in the arch. Why not extend it to provide this functionality? Also I just checked the function for BSD (Beej's Guide) and in the Windows WinSock reference. On the first look, they seem to have the same interface, so where is the platform dependence? Even the returned struct is exactly alike.
I thought doing it in HTTP to avoid unexpected crashes. But the changes could be done in a spawned branch from develop to avoid unstability in develop until it's properly tested
Oh, I see. I prefer the additional branch approach, as it minimizes rework as soon as the feature is finished.
