589
edits
Privacy/Reviews/ThunderbirdBigFiles: Difference between revisions
Privacy/Reviews/ThunderbirdBigFiles (view source)
Revision as of 15:53, 29 March 2012
, 29 March 2012→Architecture
| Line 32: | Line 32: | ||
'''The main objective of this feature/product is: | '''The main objective of this feature/product is: | ||
* store large file attachments in online storage | * store large file attachments in online storage | ||
* cooperating with service providers on both a technical and business side | * cooperating with service providers on both a technical and business side | ||
* can be pulblic services or private (ie. local ftp) | * can be pulblic services or private (ie. local ftp) | ||
* Files are uploaded when you attach them, | * Files are uploaded when you attach them, and normal attachments can be converted to online attachments from the compose window attachment pane. | ||
* "attachment" UI | * "attachment" UI | ||
* receiving a mail would have a link with some annotations created by Thunderbird. | * receiving a mail would have a link with some annotations created by Thunderbird. | ||
| Line 46: | Line 43: | ||
== Components == | == Components == | ||
Each big file provider is | Each big file provider is an XPCOM component. The mail compose code uses the nsIMsgCloudFileProvider.idl interface to talk to the big file provider. The big file providers then use their own API to talk to their servers. This communication is specific to each provider. The general flow is authentication of the user, followed by uploading of file contents, and retrieval of a link to the shared file. This link is then included in the e-mail sent to the mail recipients. | ||
There is also UI to provision accounts, and UI to control account settings. This UI is specific to each provider. | |||
=== Component X === | === Component X === | ||