bluetooth: Stub out BluetoothGattRemoteServer.

Source/modules/bluetooth/BluetoothGATTRemoteServer.h

Index: Source/modules/bluetooth/BluetoothGATTRemoteServer.h
diff --git a/Source/modules/bluetooth/BluetoothGATTRemoteServer.h b/Source/modules/bluetooth/BluetoothGATTRemoteServer.h
new file mode 100644
index 0000000000000000000000000000000000000000..584d67de239c2996555c104d4a9703cf3988a876
--- /dev/null
+++ b/Source/modules/bluetooth/BluetoothGATTRemoteServer.h
@@ -0,0 +1,25 @@
+// 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 BluetoothGATTRemoteServer_h
+#define BluetoothGATTRemoteServer_h
+
+#include "bindings/core/v8/ScriptWrappable.h"
+#include "platform/heap/Heap.h"
+#include "wtf/text/WTFString.h"
+
+namespace blink {
+
+// BluetoothGATTRemoteServer provides a way to interact with a connected bluetooth peripheral.
+class BluetoothGATTRemoteServer final
+    : public GarbageCollectedFinalized<BluetoothGATTRemoteServer>

[Jeffrey Yasskin, 2015/04/14 01:39:22]

Can we avoid finalization here? BluetoothDevice.gattServer will keep this object
alive as long as the BluetoothDevice is alive, so we only need to have
finalization on 1 piece of the whole graph in order to let the Browser know that
this renderer doesn't need the device anymore.

Then again, the Oilpan doc says to use finalization when in doubt, and I don't
know that we'll avoid all C++ objects in the members here.

[scheib, 2015/04/14 18:25:42]

Drop Finalized until/unless we need it.

[ortuno, 2015/04/14 19:31:21]

Done.

+    , public ScriptWrappable {
+    DEFINE_WRAPPERTYPEINFO();
+public:
+    void trace(Visitor*) { }
+};
+
+} // namespace blink
+
+#endif // BluetoothDevice_h