<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<div class="moz-cite-prefix">Hi Gary,<br>
<br>
On 14/09/2012 18:44, Gary A. Mort wrote:<br>
</div>
<blockquote
cite="mid:11000867.13375057.20120914174416.50536cf0ecf6e7.40802890@mail13.us4.mandrillapp.com"
type="cite">
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
<font face="Lucida Sans" size="3">
<div style="font-family:Lucida Sans;font-size:16px;">As an
example, you send it is an cool little feature - but the way
it was written, if someone else wants to store files on a
different service they need to write a completely new add on.
If instead a generalized file handling API had been placed in
the core code, while the you send it specific code was in the
official add on directory - that would likely have sparked a
dozen more add ons providing similar functionality - which
leads to growth and best practices being created - instead of
odd little features only a few people use.<br>
</div>
</font></blockquote>
YouSendIt (and now Ubuntu One and soon box.com) are providers that
are shipped with Thunderbird by default. There is a <a
href="https://developer.mozilla.org/en-US/docs/Thunderbird/Filelink_Providers">generalized
file handling API</a> already existing that those providers use.
We also have the <a
href="https://addons.mozilla.org/en-US/thunderbird/addon/dropbox-for-filelink/">Dropbox
add-on</a> that gives an example of a different provider but that
is actually using that API in an add-on.<br>
<br>
Generally with features like this, we have typically tried to allow
add-ons the possibility to hook in, or for external data to be added
(such as in the case of the ISP database).<br>
<br>
Mark.<br>
</body>
</html>