Refactor FileIO to the new design

ppapi/api/trusted/ppb_file_io_trusted.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 the trusted file IO interface
  */
 
 label Chrome {
   M14= 0.4

[raymes, 2012/11/26 22:30:54]

Please fix the spacing while you're here (to M14 = 0.4)

[victorhsieh, 2012/11/27 09:44:42]

Done.

 };
 
 // Available only to trusted implementations.
 interface PPB_FileIOTrusted {
   /**
    * Returns a file descriptor corresponding to the given FileIO object. On
    * Windows, returns a HANDLE; on all other platforms, returns a POSIX file
    * descriptor. The FileIO object must have been opened with a successful
    * call to FileIO::Open.  The file descriptor will be closed automatically
    * when the FileIO object is closed or destroyed.
    */
+  [deprecate=0.5]

[raymes, 2012/11/26 22:30:54]

You need to add 0.5 to the "label Chrome" above to get it to generate the api.

[raymes, 2012/11/26 22:33:45]

Also I'm curious what the background is behind this being deprecated?

[brettw, 2012/11/26 23:38:45]

This was only used to implement the SRPC NaCl proxy.

[victorhsieh, 2012/11/27 09:44:42]

Even with 0.5 label above, the generator won't generate the code, until you add
another function for 0.5.

[raymes, 2012/11/27 16:41:30]

Interesting. It worked for me when I recently revved the flash interface but I
have definitely seen it not work in the past. Anyhow it is no big deal for now
since we aren't deprecating the function.

   int32_t GetOSFileDescriptor([in] PP_Resource file_io);
 
   /**
    * Notifies the browser that underlying file will be modified.  This gives
    * the browser the opportunity to apply quota restrictions and possibly
    * return an error to indicate that the write is not allowed.
    */
   int32_t WillWrite([in] PP_Resource file_io,
                     [in] int64_t offset,
                     [in] int32_t bytes_to_write,
                     [in] PP_CompletionCallback callback);
 
   /**
    * Notifies the browser that underlying file will be modified.  This gives
    * the browser the opportunity to apply quota restrictions and possibly
    * return an error to indicate that the write is not allowed.
    *
    * TODO(darin): Maybe unify the above into a single WillChangeFileSize
    * method?  The above methods have the advantage of mapping to PPB_FileIO
    * Write and SetLength calls.  WillChangeFileSize would require the caller to
    * compute the file size resulting from a Write call, which may be
    * undesirable.
    */
   int32_t WillSetLength([in] PP_Resource file_io,
                         [in] int64_t length,
                         [in] PP_CompletionCallback callback);
 
 };