src: add multi-context support

This commit makes it possible to use multiple V8 execution contexts
within a single event loop.  Put another way, handle and request wrap
objects now "remember" the context they belong to and switch back to
that context when the time comes to call into JS land.

This could have been done in a quick and hacky way by calling
v8::Object::GetCreationContext() on the wrap object right before
making a callback but that leaves a fairly wide margin for bugs.

Instead, we make the context explicit through a new Environment class
that encapsulates everything (or almost everything) that belongs to
the context.  Variables that used to be a static or a global are now
members of the aforementioned class.  An additional benefit is that
this approach should make it relatively straightforward to add full
isolate support in due course.

There is no JavaScript API yet but that will be added in the near
future.

This work was graciously sponsored by GitHub, Inc.

1 files changed, 7 insertions, 3 deletions

diff --git a/src/tcp_wrap.h b/src/tcp_wrap.h
index 374458b78d..b1fa4c7f8f 100644
--- a/src/tcp_wrap.h
+++ b/src/tcp_wrap.h
@@ -21,20 +21,24 @@
 
 #ifndef SRC_TCP_WRAP_H_
 #define SRC_TCP_WRAP_H_
+
+#include "env.h"
 #include "stream_wrap.h"
 
 namespace node {
 
 class TCPWrap : public StreamWrap {
  public:
-  static v8::Local<v8::Object> Instantiate();
+  static v8::Local<v8::Object> Instantiate(Environment* env);
   static TCPWrap* Unwrap(v8::Local<v8::Object> obj);
-  static void Initialize(v8::Handle<v8::Object> target);
+  static void Initialize(v8::Handle<v8::Object> target,
+                         v8::Handle<v8::Value> unused,
+                         v8::Handle<v8::Context> context);
 
   uv_tcp_t* UVHandle();
 
  private:
-  explicit TCPWrap(v8::Handle<v8::Object> object);
+  TCPWrap(Environment* env, v8::Handle<v8::Object> object);
   ~TCPWrap();
 
   static void New(const v8::FunctionCallbackInfo<v8::Value>& args);