It seems that you catch not the exception you wanna catch out there 🙂 if the s is a socket.socket() object, then the right way to call .connect would be: import socket s = socket.socket() address=”127.0.0.1″ port = 80 # port number is a number, not string try: s.connect((address, port)) # originally, it was # … Read more
I assume you are using TCP sockets for the client-server interaction? One way to send different types of data to the server and have it be able to differentiate between the two is to dedicate the first byte (or more if you have more than 256 types of messages) as some kind of identifier. If … Read more
I believe you want to use the remote address instead: csocket.getRemoteSocketAddress().toString();
If you need 200ms for each of the 65536 ports (in the worst case, a firewall is blocking everything, thus making you hit your timeout for every single port), the maths is pretty simple: you need 13k seconds, or about 3 hours and a half. You have 2 (non-exclusive) options to make it faster: reduce … Read more
< and > are usually used to redirect IOs. What does it mean there? Is it usable in another context? How? It’s the same – input and output is redirected to fd 5. Why does it work, while /dev/tcp doesn’t exists? It’s a special file: If host is a valid hostname or Internet address, and … Read more
Death of a socket changes its behavior in several ways, so these methods are both valid 🙂 With both methods you actually check those parts of the socket’s behavior that change after disconnection. I don’t really understand his statement about calling Receive() to make sure that the remote endpoint has actually received all the data … Read more
I’ve been reading the The ultimate SO_LINGER page, or: why is my tcp not reliable blog post a lot. I recommend you read it too. It discusses edge cases of large data transfers with regards to TCP sockets. I’m not the expert at SO_LINGER, but on my server code (still in active development) I do … Read more
Since this is ‘getting started’ my answer will stick with a simple implementation rather than a highly scalable one. It’s best to first feel comfortable with the simple approach before making things more complicated. 1 – Binding and listening Your code seems fine to me, personally I use: serverSocket.Bind(new IPEndPoint(IPAddress.Any, 4444)); Rather than going the … Read more
In your example client, you don’t seem to be reading the result from the server. When I add code to do that, I see the results from the server. Also, take a look at how I used defer and break to make the reader goroutine exit. Server package main import ( “log” “net” ) func … Read more
You have two options: Use Cygwin (Unix emulation library). Port to Winsock (Windows standard library). Cygwin: lets you compile your Unix sources mostly untouched, but ties you to the Cygwin emulation library. This have two implications: general performance -no only network- will probably be less than optimal; and the target environment must have (at run … Read more