| Index: mojo/services/tracing/public/cpp/tracing_impl.h
|
| diff --git a/mojo/services/tracing/public/cpp/tracing_impl.h b/mojo/services/tracing/public/cpp/tracing_impl.h
|
| index 648023f887c2b05209c890d8e989b9bfd2f92e38..b832ef499360760956a65fed90256a134ec5e416 100644
|
| --- a/mojo/services/tracing/public/cpp/tracing_impl.h
|
| +++ b/mojo/services/tracing/public/cpp/tracing_impl.h
|
| @@ -15,6 +15,16 @@ namespace mojo {
|
| class ApplicationConnection;
|
| class ApplicationImpl;
|
|
|
| +// Connects to mojo:tracing during your Application's Initialize() call once
|
| +// per process.
|
| +//
|
| +// We need to deal with multiple ways of packaging mojo applications
|
| +// together. We'll need to deal with packages that use the mojo.ContentHandler
|
| +// interface to bundle several Applciations into a single physical on disk
|
| +// mojo binary, and with those same services each in their own mojo binary.
|
| +//
|
| +// Have your bundle ContentHandler own a TracingImpl, and each Application own
|
| +// a TracingImpl. In bundles, the second TracingImpl will be a no-op.
|
| class TracingImpl : public InterfaceFactory<tracing::TraceProvider> {
|
| public:
|
| TracingImpl();
|
|
|