184
edits
JSFileApi: Difference between revisions
+ Problems not addressed by this API
(→Writing: Optional arguments) |
(+ Problems not addressed by this API) |
||
| Line 19: | Line 19: | ||
traversing a directory; | traversing a directory; | ||
- input/output attempts to play much more nicely with JavaScript, by using JavaScript low-level data structures designed for this task (and which didn't exist when the nsIFile API was designed). | - input/output attempts to play much more nicely with JavaScript, by using JavaScript low-level data structures designed for this task (and which didn't exist when the nsIFile API was designed). | ||
= Problems not addressed by this API = | |||
This API is synchronous. This API does not attempt to solve any asynchronicity issue. Consequently, this API is not meant to be used in the main thread. See [https://bugzilla.mozilla.org/show_bug.cgi?id=691309|bug 691309] for one discussion (among many) on how to remove IO from the main thread. | |||
Note that it is quite possible to build an asynchronous file API based on this API. This is quite simple, and the process of building an async API on top of a sync API may be the best way to obtain within a finite time a cross-platform asynchronous API that works. | |||