Introduce RegistrationServer.

client/registration_response_win.h

Index: client/registration_response_win.h
diff --git a/test/paths_win.cc b/client/registration_response_win.h
similarity index 72%
copy from test/paths_win.cc
copy to client/registration_response_win.h
index 95d0264ed82ab36cf0e541315528d44585f4bbb8..5c5904b1cf7da19efd90b6dd869111966efe8d91 100644
--- a/test/paths_win.cc
+++ b/client/registration_response_win.h
@@ -12,19 +12,18 @@
 // See the License for the specific language governing permissions and
 // limitations under the License.
 
-#include "test/paths.h"
+#ifndef CRASHPAD_CLIENT_REGISTRATION_RESPONSE_WIN_H_
+#define CRASHPAD_CLIENT_REGISTRATION_RESPONSE_WIN_H_
 
 #include <windows.h>
 
 namespace crashpad {
-namespace test {
 
-// static
-base::FilePath Paths::Executable() {
-  wchar_t executable_path[_MAX_PATH];
-  GetModuleFileName(nullptr, executable_path, sizeof(executable_path));
-  return base::FilePath(executable_path);
-}
+struct RegistrationResponse {

[Mark Mentovai, 2015/05/05 20:20:33]

Is there a compelling reason to separate the request and response into their own
headers? It seems that they’ll always be used in concert.

[erikwright (departed), 2015/05/20 17:10:15]

No problem. Do you have an opinion on the name of the file that contains both?

client_registration_messages.h?

+  HANDLE request_report_event;
+  HANDLE report_complete_event;
+};
 
-}  // namespace test
 }  // namespace crashpad
+
+#endif  // CRASHPAD_CLIENT_REGISTRATION_RESPONSE_WIN_H_