Node 0.11.x support

With these changes, node_mdns builds and runs under Node 0.11.14 and nan 1.3 although I cannot say with certainty as amount of testing it received with these changes is too little.
I'm investigating now. There are two options, either I omitted it by accident or it is impossible to have there because it makes some overload indistinguishable.

On October 22, 2014 6:27:00 PM EEST, David Siegel <notifications@github.com> wrote:
>>      ServiceRef * serviceRef = static_cast<ServiceRef*>(context);
>>      Handle<Function> callback = serviceRef->GetCallback();
>>      Handle<Object> this_ = serviceRef->GetThis();
>>  
>>      const size_t argc(8);
>>      Local<Value> args[argc];
>> -    args[0] = Local<Object>::New(serviceRef->handle_);
>> -    args[1] = Integer::New(flags);
>> -    args[2] = Integer::NewFromUnsigned(interfaceIndex);
>> -    args[3] = Integer::New(errorCode);
>> +    args[0] = NanNew(NanObjectWrapHandle(serviceRef));
>> +    args[1] = NanNew<Integer>(flags);
>> +    args[2] = NanNew<Integer>(interfaceIndex);
>
>Thanks for the explanation, @kkoopa. I'm still wondering why nan
>doesn't expose `Integer::NewFromUnsigned` by specializing:
>
>````
>NAN_INLINE v8::Local<v8::Integer> NanNew(unsigned int val) {
>    return v8::Integer::NewFromUnsigned(val);
>  }
>````
>
>I mean `NanNew(...)` seems already pretty damn well specialized,
>overloaded and whatnot. I kinda thought the point was to *bind them
>all*. `Integer::NewFromUnsigned` just seems to be missing.
>
>However, thanks for the heads up!
>
>---
>Reply to this email directly or view it on GitHub:
>https://github.com/agnat/node_mdns/pull/99/files#r19220964