The moz-torrent protocol scheme wouldn't work quite like that. It would simply
be a way of taking the information in the .torrent file and encoding it in a
URI. The protocol handler implementation would then take the information in the
URI and use it to get the actual data. Just a way of passing data from the
application to the network layer.
But yes, if you concocted a moz-torrent uri of the sort that we would construct
from a .torrent file then you could get the content to render inline.
> So an http:// .../foo. torrent file would be downloaded
Yes, if you click on that link.
> but a moz-torrent:http:// .../foo. torrent file would be rendered inline, right?
The moz-torrent protocol scheme wouldn't work quite like that. It would simply
be a way of taking the information in the .torrent file and encoding it in a
URI. The protocol handler implementation would then take the information in the
URI and use it to get the actual data. Just a way of passing data from the
application to the network layer.
But yes, if you concocted a moz-torrent uri of the sort that we would construct
from a .torrent file then you could get the content to render inline.