From 200d21c3fa40c285a0989509ccb822ac163cb99d Mon Sep 17 00:00:00 2001 From: David Davies-Payne Date: Thu, 5 May 2016 18:34:11 +1200 Subject: [PATCH] Minor documentation fix: "owns" -> "own" --- README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/README.md b/README.md index 3505f5b..ddf760a 100644 --- a/README.md +++ b/README.md @@ -276,7 +276,7 @@ GCDWebServer's architecture consists of only 4 core classes: Implementing Handlers ===================== -GCDWebServer relies on "handlers" to process incoming web requests and generating responses. Handlers are implemented with GCD blocks which makes it very easy to provide your owns. However, they are executed on arbitrary threads within GCD so __special attention must be paid to thread-safety and re-entrancy__. +GCDWebServer relies on "handlers" to process incoming web requests and generating responses. Handlers are implemented with GCD blocks which makes it very easy to provide your own. However, they are executed on arbitrary threads within GCD so __special attention must be paid to thread-safety and re-entrancy__. Handlers require 2 GCD blocks: * The ```GCDWebServerMatchBlock``` is called on every handler added to the ```GCDWebServer``` instance whenever a web request has started (i.e. HTTP headers have been received). It is passed the basic info for the web request (HTTP method, URL, headers...) and must decide if it wants to handle it or not. If yes, it must return a new ```GCDWebServerRequest``` instance (see above) created with this info. Otherwise, it simply returns nil.