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

  • SEARCH
  • Home
  • 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 4050230
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Editorial Team
Asked: May 20, 20262026-05-20T14:02:39+00:00 2026-05-20T14:02:39+00:00

Alright, I found out in this question that polling sockets does not scale, so

  • 0

Alright, I found out in this question that polling sockets does not scale, so I’ve decided to look into asynchronous sockets, and I have several questions.

  1. If I have several hundred clients all trying to send data to their partner, what would be the best async method to use? select() poll() or can I just call recv() on a non-blocking socket?
  2. When I poll and find there is data to read, should I spawn a thread to take care of it?
  3. Should I worry about any sleep function, or should I just let the program take 100% CPU?
  4. Would it be efficient at all to put this whole functionality into a class? I would really like to do something like this:

//thread 1:  
while(!quit){  
   manager.check_clients();  
   manager.handle_clients();  
   manager.display_clients();  
 }
//thread 2:
while(!quit)
  manager.manage_admin_input();
  • 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-20T14:02:39+00:00Added an answer on May 20, 2026 at 2:02 pm

    The choice of polling method is OS dependent. On linux, use epoll, preferrably edge-triggered. On FreeBSD, use kqueue. On Windows, use e.g. WSAEventSelect and WSAWaitForMultipleEvents.

    Your main loop should simply be:

    for (;;) {
      epoll(); // blocking poll until an event happens, optionally with a timeout
      // iterate signaled sockets and process data
      // Other tasks
    }
    

    Whether you choose to implement this in each thread in a thread pool, or just once in the main thread, is dependent on the rest of your application. The key is to let the polling function do the wait, this way you won’t use excessive CPU.

    You can either use non-blocking sockets, or ioctl(FIONREAD... to check how much data is readable on each socket.

    My preferred OOP design for socket handling is to make a socket completely unaware of the socket poller. A socket poller, hiding the actual function used for polling, would accept sockets and the events it should watch for, do it’s polling in e.g. a tick() function, then tell each socket or an external listening class that there’s stuff to do with the socket. Something like:

    class SocketPoller {
    public:
      void registerSocket(Socket * s, int EventMask);
      void unregisterSocket(Socket * s);
      virtual void tick() = 0;
    }
    
    class SocketPollerEPoll : public SocketPoller {
    public:
      void tick() {
        epoll(...); 
        // for each socket with events:
          TheSocket->notifyReadable();
      }
    };
    
    class SocketPollerSelect : public SocketPoller {
    public:
      void tick() {
        select(...); 
        // for each socket with events:
          TheSocket->notifyReadable();
      }
    };
    
    • 0
    • Reply
    • Share
      Share
      • Share on Facebook
      • Share on Twitter
      • Share on LinkedIn
      • Share on WhatsApp
      • Report

Sidebar

Related Questions

No related questions found

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.