Introduce RegistrationServer.

client/registration_response_win.h

 // Copyright 2015 The Crashpad Authors. All rights reserved.
 //
 // Licensed under the Apache License, Version 2.0 (the "License");
 // you may not use this file except in compliance with the License.
 // You may obtain a copy of the License at
 //
 //     http://www.apache.org/licenses/LICENSE-2.0
 //
 // Unless required by applicable law or agreed to in writing, software
 // distributed under the License is distributed on an "AS IS" BASIS,
 // WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
 // 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_