The fact is that the client has not received any additional data for some time.
This is usually a client issue, but since we’re talking about client sessions and not remote sessions, I feel it is more likely. The client has opened the socket when the first time the client sent a client request with data.
The only issue I could think of is if the client is not receiving data from the server. I don’t see why this should be a problem, but it is one that I am sure we’ll have to look into.
What’s the worst thing you can do to your client?I dont think you should tell them you are on Deathloop. They should know what they have to do. I dont think the server can get around this.
If we think of a client as a sort of server that actually does the server’s job for us, we can easily see the problem. I think it’s the other way around too: a client is a server that we can use to send data to. I feel it is much more likely that our client is closing the socket. The socket should be open for our client, and it should be open for all of us too.
I’ll go over what I have in mind and I’ll explain the rest of it later.
I’ve done two tests that seem to show that the connection to the server is not being opened by our client. I’m trying to find out why.
My first thought is that the client is trying to close the socket after I have send my initial request. But then I also get the feeling that there are more problems here. I’m not sure if this will work for you too.
The server seems to be closing the socket for our client because the client is trying to close the server, while at the same time the socket is open to our client. To fix that, we have to open the socket to the server, and then it works. Ill go over what that means, and then Ill explain why the client is getting stuck at the socket close.
I will go over this again. I have to click the “close” button to close the socket to the client, with the “close” button being the most important one.