Add pipe implementation for OOP memory logging

chrome/common/profiling/memlog_sender_pipe_win.h

+// Copyright 2017 The Chromium Authors. All rights reserved.
+// Use of this source code is governed by a BSD-style license that can be
+// found in the LICENSE file.
+
+#ifndef CHROME_COMMON_PROFILING_MEMLOG_SENDER_PIPE_WIN_H_
+#define CHROME_COMMON_PROFILING_MEMLOG_SENDER_PIPE_WIN_H_
+
+#include <windows.h>
+
+#include "base/macros.h"
+#include "base/strings/string16.h"
+
+namespace profiling {
+
+class MemlogSenderPipe {
+ public:
+  explicit MemlogSenderPipe(const base::string16& pipe_id);

[Boris Vidolov, 2017/06/15 21:50:59]

If the wideness of the characters is the concern, I have found
FilePath::StringType to be useful, avoiding the conditional (win/POSIX) header.
What are you thoughts on passing the pipes in POSIX - using integer file id?

[brettw, 2017/06/15 22:12:21]

The Posix implementation will need an integer we parse out. We'll need to change
this around on Windows too to avoid problems with the sandbox. It's on my list
to change if we keep using native pipes.

+  ~MemlogSenderPipe();
+
+  bool Connect();
+
+  bool Send(const void* data, size_t sz);
+
+ private:
+  base::string16 pipe_id_;
+
+  HANDLE handle_;

[Boris Vidolov, 2017/06/15 21:50:59]

Again, is it possible to use some higher level class from base::, or is this too
basic of functionality to do so?

[brettw, 2017/06/15 22:12:21]

The main alternative is replacing with Mojo pipes which is what Albert keeps
asking about. I promised to look into this.

+
+  DISALLOW_COPY_AND_ASSIGN(MemlogSenderPipe);
+};
+
+}  // namespace profiling
+
+#endif  // CHROME_COMMON_PROFILING_MEMLOG_SENDER_PIPE_WIN_H_