From aec90d07ab4fb5adff3676205e65d28d9ebecdd5 Mon Sep 17 00:00:00 2001
From: GitFuture <752736341@qq.com>
Date: Wed, 11 Oct 2017 14:29:46 +0800
Subject: [PATCH] Translating... Concurrent servers -3

---
 .../tech/20171006 Concurrent Servers Part 3 - Event-driven.md   | 2 ++
 1 file changed, 2 insertions(+)

diff --git a/sources/tech/20171006 Concurrent Servers Part 3 - Event-driven.md b/sources/tech/20171006 Concurrent Servers Part 3 - Event-driven.md
index dc8e1ebb75..4fb433c9cb 100644
--- a/sources/tech/20171006 Concurrent Servers Part 3 - Event-driven.md	
+++ b/sources/tech/20171006 Concurrent Servers Part 3 - Event-driven.md	
@@ -1,6 +1,8 @@
 [Concurrent Servers: Part 3 - Event-driven][25]
 ============================================================
 
+GitFuture is Translating
+
 This is part 3 of a series of posts on writing concurrent network servers. [Part 1][26] introduced the series with some building blocks, and [part 2 - Threads][27] discussed multiple threads as one viable approach for concurrency in the server.
 
 Another common approach to achieve concurrency is called  _event-driven programming_ , or alternatively  _asynchronous_  programming [[1]][28]. The range of variations on this approach is very large, so we're going to start by covering the basics - using some of the fundamental APIs than form the base of most higher-level approaches. Future posts in the series will cover higher-level abstractions, as well as various hybrid approaches.