41 The compositor maintains a content update count for each registered 

    41 Each compositor in the system maintains its own content update count 

    42 surface that determines when content ready notifications will be 

    42 for each registered surface that determines when content ready 

    43 completed. The content update count is internally incremented by the 

    43 notifications will be completed. Therefore the content update count is

    44 compositor every time it receives a valid content update for a 

    44 considered per-surface-per-screen. The content update count is 

    45 registered surface. Frames may be skipped if the client submits 

    45 internally incremented by the compositor every time it receives a 

    46 content updates too fast, meaning that not every update is displayed 

    46 valid content update for a registered surface. Frames may be skipped 

    47 on screen. The first valid content update sets the content update 

    47 if the client submits content updates too fast, meaning that not every

    48 count to one. Updates sent before the surface is registered do not 

    48 update is displayed on screen. The first valid content update sets the

    49 affect the content update count. Content ready notifications for 

    49 content update count to one. Updates sent before the surface is 

    50 aContentUpdate = 1 will only be successfully completed after at least

    50 registered do not affect the content update count. Content ready 

    51 one content update has been received.

    51 notifications for aContentUpdate = 1 will only be successfully 

    52 completed after at least one content update has been received.