Add some more documentation from a recent ppapi discussion....

ppapi/c/pp_completion_callback.h

Index: ppapi/c/pp_completion_callback.h
===================================================================
--- ppapi/c/pp_completion_callback.h	(revision 77300)
+++ ppapi/c/pp_completion_callback.h	(working copy)
@@ -32,10 +32,14 @@
 /**
  * Any method that takes a PP_CompletionCallback has the option of completing
  * asynchronously if the operation would block.  Such a method should return
- * PP_Error_WouldBlock to indicate when the method will complete
- * asynchronously.  If the completion callback is NULL, then the operation will
- * block if necessary to complete its work.  PP_BlockUntilComplete() provides a
- * convenient way to specify blocking behavior.
+ * PP_ERROR_WOULDBLOCK to indicate when the method will complete

[brettw, 2011/03/10 18:36:21]

when -> that

+ * asynchronously.  In this case it will signal completion by invoking the
+ * supplied completion callback, which will always be invoked from the main
+ * PPAPI thread of execution.  If the method returns any other value,
+ * including PP_OK, the completion callback will not be invoked.  If the
+ * completion callback is NULL, then the method will block if necessary to
+ * complete its work.  PP_BlockUntilComplete() provides a convenient way to
+ * specify blocking behavior.
  *
  * The result parameter passes an int32_t that if negative indicates an error
  * code.  Otherwise the result value indicates success.  If it is a positive