Skip to content

Basic Networking - Part 4 #32

Description

@bonedaddy

Overview

Up until now the socket server requires two threads for operating. One accepting new connections, another to process them. This increases the resource footprint, and means that if we are using a system with a single available thread, creating more than one will lead to decreased performance. This means we need a way of handling new connections when there's only a single available thread

Expected Outcome

  • Have the ability to run the socket server using a single thread
  • this means we need to switch between performing the following tasks:
    • accepting connections
    • handling new connections

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions