Merge pull request #2 from WyriHaximus/master

Cleaned up dns repo to become standalone

Author: cboden

.gitignore

@@ -0,0 +1,2 @@
+composer.lock
+vendor

.travis.yml

@@ -0,0 +1,14 @@
+language: php
+
+php:
+  - 5.4
+  - 5.5
+  - 5.6
+  - hhvm
+
+matrix:
+  allow_failures:
+    - php: hhvm
+
+before_script:
+  - composer install --dev --prefer-source

README.md

@@ -1,5 +1,7 @@
 # Dns Component
 
+[![Build Status](https://secure.travis-ci.org/reactphp/dns.png?branch=master)](http://travis-ci.org/reactphp/dns)
+
 Async DNS resolver.
 
 The main point of the DNS component is to provide async DNS resolution.
@@ -12,20 +14,23 @@ The most basic usage is to just create a resolver through the resolver
 factory. All you need to give it is a nameserver, then you can start resolving
 names, baby!
 
+```php
     $loop = React\EventLoop\Factory::create();
     $factory = new React\Dns\Resolver\Factory();
     $dns = $factory->create('8.8.8.8', $loop);
 
     $dns->resolve('igor.io')->then(function ($ip) {
         echo "Host: $ip\n";
     });
+```
 
 But there's more.
 
 ## Caching
 
 You can cache results by configuring the resolver to use a `CachedExecutor`:
 
+```php
     $loop = React\EventLoop\Factory::create();
     $factory = new React\Dns\Resolver\Factory();
     $dns = $factory->createCached('8.8.8.8', $loop);
@@ -39,6 +44,7 @@ You can cache results by configuring the resolver to use a `CachedExecutor`:
     $dns->resolve('igor.io')->then(function ($ip) {
         echo "Host: $ip\n";
     });
+```
 
 If the first call returns before the second, only one query will be executed.
 The second result will be served from cache.

composer.json

@@ -10,7 +10,7 @@
         "react/promise": "~2.0"
     },
     "autoload": {
-        "psr-4": { "React\\Dns\\": "" }
+        "psr-4": { "React\\Dns\\": "src" }
     },
     "extra": {
         "branch-alias": {