Implement Pepper PPB_VideoDecoder interface.

ppapi/api/pp_errors.idl

 /* Copyright (c) 2012 The Chromium Authors. All rights reserved.
  * Use of this source code is governed by a BSD-style license that can be
  * found in the LICENSE file.
  */
 
 /**
  * This file defines an enumeration of all PPAPI error codes.
  */
 
 /**
@@ skipping 67 matching lines @@
    */
   PP_ERROR_NOTSUPPORTED = -12,
 
   /**
    * Returned if you try to use a null completion callback to "block until
    * complete" on the main thread. Blocking the main thread is not permitted
    * to keep the browser responsive (otherwise, you may not be able to handle
    * input events, and there are reentrancy and deadlock issues).
    */
   PP_ERROR_BLOCKS_MAIN_THREAD = -13,
+  /**
+   * This value indicates that plugin sent malformed input data to the browser.
+   */
+  PP_ERROR_MALFORMED_INPUT = -14,
+  /**
+   * This value indicates that a platform failure occurred. This means that the
+   * plugin's request was valid but the browser could not complete it. Some

[yzshen1, 2014/05/15 00:55:30]

Hmm.. I think we have a lot of cases in which plugin makes legitimate requests
but the browser is not able to complete. For example, the plugin requests to
make a connection to a server, but the computer is not connected to the
internet; or the plugin makes a reasonable memory request but the system is
reaching its resource limit.

I feel that in such cases we either want to give a more specific error code, for
example, PP_ERROR_ADDRESS_UNREACHABLE and PP_ERROR_NOMEMORY; or we use the most
generic error code PP_ERROR_FAILED.

With regard to "bugs in the browser", it seems a little weird to make an error
code for it. We probably need to fix the bugs instead. 

Maybe we could make an error code specific to "hardware/driver limitations"?

What do you think?

[bbudge, 2014/05/15 01:19:18]

I've changed the docs. I think the unique thing about this error is that when a
resource returns it, it has become unusable. We could change the name to
PP_ERROR_UNRECOVERABLE_ERROR if you like.

I think for VideoDecoder, returning PP_ERROR_FAILED will be confusing since the
plugin can't determine whether it made a bad call, or whether the resource has
died.

[yzshen1, 2014/05/15 17:07:22]

Yes, PP_ERROR_UNRECOVERABLE_ERROR sounds easier to understand to me.

+   * causes of platform failures are hardware and driver limitations, and bugs
+   * in the browser.
+   */
+  PP_ERROR_PLATFORM_FAILED = -15,
 
   /** This value indicates failure due to a file that does not exist. */
   PP_ERROR_FILENOTFOUND   = -20,
   /** This value indicates failure due to a file that already exists. */
   PP_ERROR_FILEEXISTS     = -21,
   /** This value indicates failure due to a file that is too big. */
   PP_ERROR_FILETOOBIG     = -22,
   /**
    * This value indicates failure due to a file having been modified
    * unexpectedly.
@@ skipping 76 matching lines @@
   /**
    * This value indicates that the message was too large for the transport.
    */
   PP_ERROR_MESSAGE_TOO_BIG = -109,
   /**
    * This value indicates that the host name could not be resolved.
    */
   PP_ERROR_NAME_NOT_RESOLVED = -110
 };