Sign Up

Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.

Have an account? Sign In

Have an account? Sign In Now

Sign In

Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.

Sign Up Here

Forgot Password?

Don't have account, Sign Up Here

Forgot Password

Lost your password? Please enter your email address. You will receive a link and will create a new password via email.

Have an account? Sign In Now

You must login to ask a question.

Forgot Password?

Need An Account, Sign Up Here

Please briefly explain why you feel this question should be reported.

Please briefly explain why you feel this answer should be reported.

Please briefly explain why you feel this user should be reported.

Sign InSign Up

The Archive Base

The Archive Base Logo The Archive Base Logo

The Archive Base Navigation

  • Home
  • SEARCH
  • About Us
  • Blog
  • Contact Us
Search
Ask A Question

Mobile menu

Close
Ask a Question
  • Home
  • Add group
  • Groups page
  • Feed
  • User Profile
  • Communities
  • Questions
    • New Questions
    • Trending Questions
    • Must read Questions
    • Hot Questions
  • Polls
  • Tags
  • Badges
  • Buy Points
  • Users
  • Help
  • Buy Theme
  • SEARCH
Home/ Questions/Q 833341
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Editorial Team
Asked: May 15, 20262026-05-15T04:30:11+00:00 2026-05-15T04:30:11+00:00

I’m trying to make a MFC application(client) that connects to a server on (localhost,port

  • 0

I’m trying to make a MFC application(client) that connects to a server on (“localhost”,port 1234), the server replies to the client and the client reads from the server’s response.

The server is able to receive the data from the client and it sends the reply back to the socket from where it received it, but I am unable to read the reply from within the client.

I am making a CAsyncSocket to connect to the server and send data and a CAsyncSocket with overloaded methods onAccet and onReceive to read the reply from the server.
Please tell me what I’m doing wrong.

    class ServerSocket:public CAsyncSocket{
    public:
    void OnAccept(int nErrorCode){
        outputBox->SetWindowTextA("RECEIVED DATA");
        CAsyncSocket::OnAccept(nErrorCode);
    }
};

//in ApplicationDlg I have:

socket.Create();
socket.Connect("127.0.0.1",1234);
socket.Send(temp,strlen(temp));    //this should be sending the initial message

if(!serverSocket.Create())  //this should get the response i guess...
    AfxMessageBox("Could not create server socket");

if(!serverSocket.Listen())
    AfxMessageBox("Could not listen to socket");
  • 1 1 Answer
  • 0 Views
  • 0 Followers
  • 0
Share
  • Facebook
  • Report

Leave an answer
Cancel reply

You must login to add an answer.

Forgot Password?

Need An Account, Sign Up Here

1 Answer

  • Voted
  • Oldest
  • Recent
  • Random
  1. Editorial Team
    Editorial Team
    2026-05-15T04:30:12+00:00Added an answer on May 15, 2026 at 4:30 am

    You should be aware that all network operations are potentially time-consuming operations. Now, since you’re using MFC’s CAsyncSocket class, it performs all the operations asynchronously (doesn’t block you). But return from the function doesn’t mean it’s already completed.

    Let’s look at the following lines of code:

    socket.Connect("127.0.0.1",1234);
    socket.Send(temp,strlen(temp));    //this should be sending the initial message
    

    The first is the call to Connect, which most probably doesn’t complete immediately.
    Next, you call Send, but your socket isn’t connected yet! It definitely returns you an error code, but since you don’t bother checking its return value – you just happily wait to receive something.

    So, the next rule for you, my friend, should be checking every return value for every function that you call, especially when it comes to networking where errors are legitimate and happen frequently.

    You should only start sending after OnConnect has been called.

    • 0
    • Reply
    • Share
      Share
      • Share on Facebook
      • Share on Twitter
      • Share on LinkedIn
      • Share on WhatsApp
      • Report

Sidebar

Explore

  • Home
  • Add group
  • Groups page
  • Communities
  • Questions
    • New Questions
    • Trending Questions
    • Must read Questions
    • Hot Questions
  • Polls
  • Tags
  • Badges
  • Users
  • Help
  • SEARCH

Footer

© 2021 The Archive Base. All Rights Reserved
With Love by The Archive Base

Insert/edit link

Enter the destination URL

Or link to existing content

    No search term specified. Showing recent items. Search or use up and down arrow keys to select an item.