Confirmed users
2
edits
Add-ons/dataDirectory: Difference between revisions
Techlive Zheng's comments
(Techlive Zheng's comments) |
|||
| Line 45: | Line 45: | ||
* (Yoric) Please design your data directory so that it can be accessed from chrome worker threads. | * (Yoric) Please design your data directory so that it can be accessed from chrome worker threads. | ||
* (Yoric) When time comes to make writes shutdown-safe, please come and talk to me. | * (Yoric) When time comes to make writes shutdown-safe, please come and talk to me. | ||
* (techlivezheng) As long as the add-on places its data in the data directory, no limitation should be set on size or the file type. | |||
* (techlivezheng) The removal of the data directory should be left to the add-on author to decide. Some add-ons, e.g. session manager or scrapbook, their data is very important. No automatic clean-up should be scheduled, though it is nice to have a UI interface to show the left over data directories for user to manage. On profile reset, the data directories should be cleared, or at least, move and backup them in another place. | |||
* (techlivezheng) "We'll need to sanitize the add-on id a little bit here; if an add-on id contains a slash, that's not a good thing." Absolutely. | |||
* (techlivezheng) "Do we want to enforce the existence of the extension-data directory itself, so that add-on providers don't have to create that folder too?" This should be smart, if a write action is taken through the API, then the directory should be created automatically. | |||