Mojo cpp bindings: add support for validating incoming messages.

mojo/public/cpp/bindings/lib/router.cc

Index: mojo/public/cpp/bindings/lib/router.cc
diff --git a/mojo/public/cpp/bindings/lib/router.cc b/mojo/public/cpp/bindings/lib/router.cc
index ec68bba9459bf2b73754a9ee1ec648022ebb1227..212787d534e40e696bf4016642689e13294e4fe4 100644
--- a/mojo/public/cpp/bindings/lib/router.cc
+++ b/mojo/public/cpp/bindings/lib/router.cc
@@ -62,13 +62,17 @@ bool Router::HandleIncomingMessageThunk::AcceptWithResponder(
 
 // ----------------------------------------------------------------------------
 
-Router::Router(ScopedMessagePipeHandle message_pipe, MojoAsyncWaiter* waiter)
-    : connector_(message_pipe.Pass(), waiter),
+Router::Router(ScopedMessagePipeHandle message_pipe,
+               ValidatorChain validators,
+               MojoAsyncWaiter* waiter)
+    : thunk_(this),
+      validators_(validators.Pass()),
+      connector_(message_pipe.Pass(), waiter),
       weak_self_(this),
       incoming_receiver_(NULL),
-      thunk_(this),
       next_request_id_(0) {
-  connector_.set_incoming_receiver(&thunk_);
+  validators_.set_sink(&thunk_);
+  connector_.set_incoming_receiver(validators_.GetHead());

[darin (slow to review), 2014/05/12 17:39:11]

Oh, I see an issue with my suggestion. Router wants to insert a MessageReceiver
(thunk_) between the stub (i.e., incoming_receiver_) and the validators. In that
case, we do need to specify the validators separately from the incoming
receiver. OK.

 }
 
 Router::~Router() {