Click here to Skip to main content
13,259,847 members (51,744 online)
Click here to Skip to main content
Add your own
alternative version


40 bookmarked
Posted 20 Jul 2010

Another TCP echo server using IOCP

, 27 Mar 2013
Rate this:
Please Sign up or sign in to vote.
An introduction to writing IOCP network servers


This tip shows a very simple non-blocking TCP echo server using Windows Input/Output Completion Ports, capable of handling any number of clients simultaneously.


IOCPs are generally considered the best (some would say the only) way of writing high-performance, highly-scalable network servers in Windows. But there are no simple examples of their use readily available in the internet.
This tip intends to fulfill this gap, by providing a very simple C-language IOCP server example. There are no classes to learn, no other Windows API to worry about, no thread stuff to complicate matters, just the two functions relating to IOCPs: CreateIoCompletionPort and GetQueuedCompletionStatus. Also, of course, the usual sockets API are used, in the Winsock asynchronous flavor: AcceptEx, listen, bind, WSARecv and WSASend.


The general flow of control of the echo server is described in the steps below:
1. initialize Winsock (WSAStartup)
2. create the I/O Completion Port (CreateIoCompletionPort)
3. create the listening socket (listen)
4. associate the listening socket with the IOCP (CreateIoCompletionPort)
5. bind the listening socket (bind)
6. start listening (listen)
7. create a pointer to the AcceptEx function (!)
8. start accepting a new connection (asynchronous AcceptEx)
   // the completion status for AcceptEx will be reported through
   // the listen IOCP completion status (see step 4)
9. wait for a completion port status (GetQueuedCompletionStatus)
9.1 if the completion status is for an accept (an AcceptEx has completed)
    9.1.1 "update the context" of the new socket (whatever that is...)
    9.1.2 associate the new socket with the completion port
    9.1.3 start reading from the new socket (asynchronous WSARecv)
    9.1.4 start accepting another connection (asynchronous AcceptEx)
    9.1.5 go to step 9
9.2 if the completion status is for a read (a WSARecv has completed)
    9.2.1 start writing to the socket through which the data arrived,
          echoing back the data (asynchronous WSASend)
    9.2.2 go to step 9
9.3 if the completion status is for a write (a WSASend has completed)
    9.3.1 start reading again from the socket that was used to send the data
          (asynchronous WSARecv)
    9.3.2 go to step 9
That's it! Well, there are all those pesky error situations that have to be handled, and there's also some code to track the connections, but all in all, the above pseudo-code sums up most of the program code. One thing to note though is that all operations must be "overlapped" (a kind of asynchronous I/O operation in Windows).
Also, there's a small client program (not using IOCPs) that can be used to test the echo server.


IOCPs are easy to use, and the program shipped with this tip intends to show how to do it.
You can download the code from here.


This article, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)


About the Author

José Vitor
Software Developer
Brazil Brazil
I'm a long-time software developer living in Brazil.

I've been developing software for retail and banking automation in C/C++ for many years now. In the old days I even did some COBOL programming, and some assembly for the 8080.

My experience ranges from low level software such as interface code for serial devices for DOS and Windows (bar code scanners, printers, cash dispensers, etc) and goes to writing end user applications for POS terminals and bank ATMs. In between I've done a great deal of TCP/IP programming using the basic Berkeley sockets interface, which is my main interest nowadays.

You may also be interested in...


Comments and Discussions

GeneralReason for my vote of 5 Simple and to the point. For quick l... Pin
Ashish Tyagi 4011-Sep-11 8:06
memberAshish Tyagi 4011-Sep-11 8:06 

General General    News News    Suggestion Suggestion    Question Question    Bug Bug    Answer Answer    Joke Joke    Praise Praise    Rant Rant    Admin Admin   

Use Ctrl+Left/Right to switch messages, Ctrl+Up/Down to switch threads, Ctrl+Shift+Left/Right to switch pages.

Permalink | Advertise | Privacy | Terms of Use | Mobile
Web02 | 2.8.171114.1 | Last Updated 27 Mar 2013
Article Copyright 2010 by José Vitor
Everything else Copyright © CodeProject, 1999-2017
Layout: fixed | fluid