Bindings layer for declarative events API

chrome/browser/extensions/api/declarative/rules_registry_dispatcher.cc

Index: chrome/browser/extensions/api/declarative/rules_registry_dispatcher.cc
diff --git a/chrome/browser/extensions/api/declarative/rules_registry_dispatcher.cc b/chrome/browser/extensions/api/declarative/rules_registry_dispatcher.cc
new file mode 100644
index 0000000000000000000000000000000000000000..a35777383b89ce78c8774f0dececb1519838686f
--- /dev/null
+++ b/chrome/browser/extensions/api/declarative/rules_registry_dispatcher.cc
@@ -0,0 +1,31 @@
+// Copyright (c) 2012 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.
+
+#include "chrome/browser/extensions/api/declarative/rules_registry_dispatcher.h"
+
+#include "base/values.h"
+
+namespace extensions {
+
+bool AddRulesFunction::RunImpl() {
+  // LOG(ERROR) << "AddRulesFunction called";
+
+  // We always return an empty list here. The binding of return values
+  // is handled in JavaScript by event.js.
+  result_.reset(new ListValue());

[Matt Perry, 2012/01/24 22:39:10]

Why do you even need to return anything?

[battre, 2012/01/25 19:25:08]

Due to the validation check according to the API defintion.

+  return true;
+}
+
+bool RemoveRulesFunction::RunImpl() {
+  // LOG(ERROR) << "RemoveRulesFunction called";
+  return true;
+}
+
+bool GetRulesFunction::RunImpl() {
+  // LOG(ERROR) << "GetRulesFunction called";
+  result_.reset(new ListValue());
+  return true;
+}
+
+}  // namespace extensions