139
edits
Jbpiacentino (talk | contribs) No edit summary |
Jbpiacentino (talk | contribs) No edit summary |
||
Line 15: | Line 15: | ||
- Are there differences in different countries ? Some consumer storage providers more popular in some countries ? | - Are there differences in different countries ? Some consumer storage providers more popular in some countries ? | ||
Use cases: | |||
- How to deal with offline mode ? | - How to deal with offline mode ? | ||
- Are there cases where TB should or could delete a file ? | - Are there cases where TB should or could delete a file ? | ||
- Should the online file make reference to the email that created it ? | - Should the online file make reference to the email that created it ? | ||
- Some online storage services have file expiration dates (on free accounts). Is it acceptable ? Can the recipients understand there is a limited lifetime to the link ? | |||
- Some providers rely on a synchronization model (Dropbox, Ubuntu one...) vs direct file access (FTP, network drive...). and recommend using an installed synchronization application. Is this a problem ? Is it mandatory (can we use web APIs for TB and let users choose to install the client if they want to ?) | - Some providers rely on a synchronization model (Dropbox, Ubuntu one...) vs direct file access (FTP, network drive...). and recommend using an installed synchronization application. Is this a problem ? Is it mandatory (can we use web APIs for TB and let users choose to install the client if they want to ?) | ||
- Does the local client helps offline use (sync happens when going online, in the background) ? | - Does the local client helps offline use (sync happens when going online, in the background) ? | ||
- Recipients must not have to register to the online service provider to have access to the online file. | |||
Implementation: | Implementation: | ||
- Senders should be able to ensure that a big file can only be viewed by the recipients of the email (this should be the default setting). Is this true possible for all providers ? | |||
- What technology for provider API implementation ? | - What technology for provider API implementation ? | ||
- Can this be done through a web app exposing web intents ? Can the web app be local ? | |||
- Each provider must be supported through an installable provider (web app or add-on), some of which are distributed by default with TB | |||
- FTP servers are difficult to set up for average users (at least to ensure security & privacy). Can this be offered to an average consumer (probably one of the the reason why online file storage are popular) | |||
- | |||
|Feature overview=This Thunderbird feature provides a way to use online storage services to store large size email file attachments. With this feature, email file attachments are replaced by urls pointing to an online file storage server, where the files can be found. | |Feature overview=This Thunderbird feature provides a way to use online storage services to store large size email file attachments. With this feature, email file attachments are replaced by urls pointing to an online file storage server, where the files can be found. | ||
Line 62: | Line 59: | ||
- Quota management<br/> | - Quota management<br/> | ||
Detect over quota situations (mostly in the case of consumer online storage services free offers) and guide towards resolution (signup for premium service, file deletions...) | Detect over quota situations (mostly in the case of consumer online storage services free offers) and guide towards resolution (signup for premium service, file deletions...) | ||
- Advanced features | |||
- Some consumer online storage services offer document tracking (YouSendIt for example). It might be interesting | |||
|Feature requirements=- APIs access to consumer & professional online storage services | |Feature requirements=- APIs access to consumer & professional online storage services | ||
|Feature non-goals=This is not a replacement to file attachment. Care should be taken to make it clear in the UX (for example through a specific UI), whilst facilitating the use of BigFiles when using 'regular' attachments. | |Feature non-goals=This is not a replacement to file attachment. Care should be taken to make it clear in the UX (for example through a specific UI), whilst facilitating the use of BigFiles when using 'regular' attachments. |
edits