Mojo: introducing a thread safe interface pointer.

mojo/public/tools/bindings/generators/cpp_templates/interface_proxy_declaration.tmpl

 {%- import "interface_macros.tmpl" as interface_macros %}
 class {{export_attribute}} {{interface.name}}Proxy
     : public {{interface.name}} {
  public:
   explicit {{interface.name}}Proxy(mojo::MessageReceiverWithResponder* receiver);
 
 {%- for method in interface.methods %}
 {%-   if method.sync %}
   bool {{method.name}}({{interface_macros.declare_sync_method_params("", method)}}) override;
 {%-   endif %}
   void {{method.name}}({{interface_macros.declare_request_params("", method)}}) override;
 {%- endfor %}
 
-  mojo::internal::SerializationContext* serialization_context() {
-    return &serialization_context_;
+  void set_group_controller(mojo::AssociatedGroupController* group_controller) {

[yzshen1, 2016/11/15 18:53:46]

I think it is preferred to avoid passing raw pointer of ref-counted object as
input?

We could use a scoped_refptr as input and then do group_controller_ =
std::move(group_controller) to avoid extra addref/release.

WDYT?

[Jay Civelli, 2016/11/15 19:36:38]

Sounds reasonable, done.

+    group_controller_ = group_controller;
   }
-
  private:
   mojo::MessageReceiverWithResponder* receiver_;
-  mojo::internal::SerializationContext serialization_context_;
+  scoped_refptr<mojo::AssociatedGroupController> group_controller_;
 };