Serialize a subset of WebInputEvents to protobufs.

blimp/common/input/input_event_conversions.h

+// Copyright 2015 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 BLIMP_COMMON_INPUT_INPUT_EVENT_CONVERSIONS_H_
+#define BLIMP_COMMON_INPUT_INPUT_EVENT_CONVERSIONS_H_
+
+#include "base/memory/scoped_ptr.h"
+#include "blimp/common/blimp_common_export.h"
+
+namespace blink {
+class WebInputEvent;
+}
+
+namespace blimp {
+
+class InputMessage;
+
+// Convert a blink::WebInputEvent to an InputMessage proto.
+BLIMP_COMMON_EXPORT void WebInputEventToProto(const blink::WebInputEvent& event,
+                                              InputMessage* proto);

[Wez, 2015/11/16 21:25:47]

In general there won't be a 1:1 correspondence between InputMessage contents and
WebInputEvent contents, e.g. we will likely streamline events on-the-wire my
removing state that doesn't change across sequences of events, such as flags.

I'd recommend having an InputMessageProcessor class in blimp/net (rather than
blimp/common) that does the InputMessage->WebInputEvent conversion, and an e.g.
InputMessageGenerator that does the corresponding WebInputEvent->InputMessage
conversion. Those can then hold state across events.

[David Trainor- moved to gerrit, 2015/11/17 01:05:00]

Ah good idea.

+
+// Convert an InputMessage proto to a blink::WebInputEvent.  |nullptr| is
+// returned if the event could not be deserialized.
+BLIMP_COMMON_EXPORT scoped_ptr<blink::WebInputEvent> ProtoToWebInputEvent(
+    const InputMessage& proto);
+
+}  // namespace blimp
+
+#endif  // BLIMP_COMMON_INPUT_INPUT_EVENT_CONVERSIONS_H_