OLD | NEW |
---|---|
(Empty) | |
1 // Copyright 2015 The Chromium Authors. All rights reserved. | |
2 // Use of this source code is governed by a BSD-style license that can be | |
3 // found in the LICENSE file. | |
4 | |
5 #ifndef CC_TREES_CHANNEL_MAIN_H_ | |
6 #define CC_TREES_CHANNEL_MAIN_H_ | |
7 | |
8 #include "cc/base/cc_export.h" | |
9 | |
10 namespace cc { | |
11 | |
12 // ChannelMain and ChannelImpl provide an abstract communication layer for | |
13 // the main and impl side of the compositor. | |
14 // | |
15 // The communication sequence between the 2 sides is: | |
enne (OOO)
2015/09/24 22:40:44
If the second diagram is just the first reversed,
Khushal
2015/09/24 23:46:50
That makes more sense. Done.
| |
16 // | |
17 // LayerTreeHost-->ProxyMain-->ChannelMain | |
18 // | | |
19 // | | |
20 // ChannelImpl-->ProxyImpl-->LayerTreeHostImpl | |
21 // | |
22 // LayerTreeHostImpl-->ProxyImpl-->ChannelImpl | |
23 // | | |
24 // | | |
25 // ChannelMain-->ProxyMain-->LayerTreeHost | |
26 | |
27 class CC_EXPORT ChannelMain { | |
28 public: | |
29 // Interface for commands sent to the ProxyImpl | |
30 virtual void SetThrottleFrameProductionOnImpl(bool throttle) = 0; | |
31 virtual void SetLayerTreeHostClientReadyOnImpl() = 0; | |
enne (OOO)
2015/09/24 22:40:44
I assume these are just a start and you'll add the
Khushal
2015/09/24 23:46:50
Yes. Just wanted to get set up the framework right
| |
32 | |
33 virtual ~ChannelMain() {} | |
34 }; | |
35 | |
36 } // namespace cc | |
37 | |
38 #endif // CC_TREES_CHANNEL_MAIN_H_ | |
OLD | NEW |