Skip to content

[WIP] Add TCP/IP networking support with fallback to double buffer - #7

Closed
corepunch with Copilot wants to merge 1 commit into
mainfrom
copilot/add-tcp-ip-networking
Closed

corepunch with Copilot wants to merge 1 commit into
mainfrom
copilot/add-tcp-ip-networking

Conversation

Copilot AI commented Jan 8, 2026 •

Copy link
Copy Markdown
Contributor
  • Analyze repository structure and understand current networking implementation
  • Add TCP/IP socket networking implementation
    • Create new functions for TCP/IP client and server sockets
    • Add connection/accept logic for TCP/IP
    • Implement read/write operations for TCP/IP
  • Add #ifdef USE_LOOPBACK to support fallback to double buffer networking
    • Wrap current loopback code with #ifdef USE_LOOPBACK
    • Make TCP/IP the default, loopback the fallback
  • Add command line argument parsing for networking mode
    • Add -server option to start as server
    • Add -client=host:port option to connect to server
    • Default behavior: create both server and client (current behavior)
  • Update main.c to handle new command line arguments
  • Test the implementation
    • Test loopback mode (current behavior)
    • Test TCP/IP server mode
    • Test TCP/IP client mode
Original prompt

Add tcp/ip networking, with #ifdef to fallback to current double buffer fake networking. Also, use command line arguments to connect to certain server or if none are provided create server and client as it's done right now


💡 You can make Copilot smarter by setting up custom instructions, customizing its development environment and configuring Model Context Protocol (MCP) servers. Learn more Copilot coding agent tips in the docs.

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

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants