Forgot a piece of README-nacl.txt
authorGabriel Jacobo
Sun, 08 Jun 2014 18:50:40 -0300
changeset 8852bb99ec3b21d8
parent 8851 a7cfe554d337
child 8853 a25dcbe4fb02
Forgot a piece of README-nacl.txt
README-nacl.txt
     1.1 --- a/README-nacl.txt	Sun Jun 08 18:18:13 2014 -0300
     1.2 +++ b/README-nacl.txt	Sun Jun 08 18:50:40 2014 -0300
     1.3 @@ -28,6 +28,10 @@
     1.4  you dump them into the SDK path, which is inconvenient).
     1.5  Also provided in test/nacl is the required support file, such as index.html, 
     1.6  manifest.json, etc.
     1.7 +SDL apps for NaCl run on a worker thread using the ppapi_simple infrastructure.
     1.8 +This allows for blocking calls on all the relevant systems (OpenGL ES, filesystem),
     1.9 +hiding the asynchronous nature of the browser behind the scenes...which is not the
    1.10 +same as making it dissapear!
    1.11  
    1.12  
    1.13  ================================================================================
    1.14 @@ -59,10 +63,24 @@
    1.15  SDL_RWops work transparently with nacl_io. Two functions are provided to control
    1.16  mount points:
    1.17      
    1.18 +    int SDL_NaClMount(const char* source, const char* target, 
    1.19 +                      const char* filesystemtype, 
    1.20 +                      unsigned long mountflags, const void *data);
    1.21 +    int SDL_NaClUmount(const char *target);
    1.22      
    1.23 -    For convenience, SDL will by default
    1.24 -mount an httpfs tree at / before calling the app's main function. Such setting
    1.25 -can be overriden by calling SDL_NaCl
    1.26 +    For convenience, SDL will by default mount an httpfs tree at / before calling 
    1.27 +the app's main function. Such setting can be overriden by calling:
    1.28 +    
    1.29 +    SDL_NaClUmount("/");
    1.30 +
    1.31 +And then mounting a different filesystem at /
    1.32 +
    1.33 +It's important to consider that the asynchronous nature of file operations on a
    1.34 +browser is hidden from the application, effectively providing the developer with
    1.35 +a set of blocking file operations just like you get in a regular desktop 
    1.36 +environment, which eases the job of porting to Native Client, but also introduces 
    1.37 +a set of challenges of its own, in particular when big file sizes and slow 
    1.38 +connections are involved.
    1.39  
    1.40  For more information on how nacl_io and mount points work, see:
    1.41