Support SSL connections in websocket-to-TCP proxy.

For historical reasons current implementation of WS-to-TCP proxy was implemented as standalone libevent-based server.
Then it was integrated into chromium as is.
In order to support SSL we need to connect libevent-based proxy with MessageLoopForIO-based chromium network stack.
We do it using pipes.

It is intended as temporary solution until we will have
new shiny implementation of WS-to-TCP proxy integrated into network stack.

BUG=chromium-os:15533
TEST=Manual

Review URL: http://codereview.chromium.org/8087001

git-svn-id: svn://svn.chromium.org/chrome/trunk/src@105515 0039d316-1c4b-4281-b951-d872f2087c98

2 files changed, 10 insertions, 1 deletions

diff --git a/net/base/io_buffer.cc b/net/base/io_buffer.cc
index aa04870..b1c72ce 100644
--- a/net/base/io_buffer.cc
+++ b/net/base/io_buffer.cc
@@ -31,6 +31,11 @@ IOBufferWithSize::IOBufferWithSize(int size)
       size_(size) {
 }
 
+IOBufferWithSize::IOBufferWithSize(char* data, int size)
+    : IOBuffer(data),
+      size_(size) {
+}
+
 IOBufferWithSize::~IOBufferWithSize() {
 }
 
diff --git a/net/base/io_buffer.h b/net/base/io_buffer.h
index 1451dec..79fedfe 100644
--- a/net/base/io_buffer.h
+++ b/net/base/io_buffer.h
@@ -46,7 +46,11 @@ class NET_EXPORT IOBufferWithSize : public IOBuffer {
 
   int size() const { return size_; }
 
- private:
+ protected:
+  // Purpose of this constructor is to give a subclass access to the base class
+  // constructor IOBuffer(char*) thus allowing subclass to use underlying
+  // memory it does not own.
+  IOBufferWithSize(char* data, int size);
   virtual ~IOBufferWithSize();
 
   int size_;