John Tytgat wrote:
In message <4caa775d71sbellon(a)sbellon.de>
Stefan Bellon <sbellon(a)sbellon.de> wrote:
> Just a fancy, but cool idea: What about adding native
> support to NetSurf? BitTorrent has a C implementation at
and it depends on OpenSSL and LibCURL which are
> both already present in NetSurf anyway.
Also e2fsprogs-devel is needed (cfr project readme file) but I
know to what extend.
I'm not sure why this is needed.
> Question to users: Is there demand for it?
> Question to developers: Would it be easy to add support for
> BitTorrent based on the MIME type or file name ending, assuming
> libBT handles the rest?
I think so but I hardly claim I fully understand all its internals.
But I fail to see this being part of a browser. Why not having a
btget standalone application ?
Just because of one reason: libBT itself is only around 90 KB in size
(RISC OS ALF file). As a plug-in (or a stand-alone tool) it would need
OpenSSL and libCURL and thus an additional 2 MB. As those libraries are
already present in NetSurf, those extra 90 KB won't be much, but
BitTorrent downloads can be downloaded transparently.
I don't know if BT has an URI associated with it, but if so, it
made that btget gets run when that URI gets requested by any
browser/mail application, or if it has a Mime/filetype/file extension
associated, you can make it runnable.
Yes, I know that. And this would normally be the way to go. But see