It is better to do one thing well than several things poorly.
Vuze is having that problem. Azeurus was a very good torrent client. However, adding all of the other stuff has made for a difficult program to support. Since Vuze is also Java based, it is not unreasonable to start both programs with one script.
The complexity of torrents is immense. BitTorrent is getting too fat. There are now several side protocols to support in addition to just the .torrent file and the multiple kinds of stream that make up a BitTorrent connection. Also, a BitTorrent client can be dealing with hundreds of peers at one time, while dealing with OS restrictions on half-connects, differences in stream formats between clients and trackers of different versions.
Shareaza started as a Gnutella 2 client, then then added Gnutella 1 and edonkey. All of them have similar protocols, so it was a reasonable goal. They have been saying they support Torrents for at least two years, but only have the job about half done.
As remi said, JD is a downloader (DDL), while a torrent client is a sharing program (p2p). These are not really compatible.
Integration has some surprisingly bad consequences. If you follow the logic, you will see that you would be making everything you download from RS available for sharing over the torrent system if there is a .torrent file for it somewhere. Any RS file that also has a torrent could be downloaded through the torrent system instead.
If they are not integrated, should they be interfaced? Most of us are short on bandwidth. It would be nice to find a fair way for the two programs to share the bandwidth. But what is fair? It would be great if a .Torrent file were just like a .DLC, except that the streaming was handled by this other piece of software. Then, when the files are downloaded, JD could perform the assembly (usually unrar). But, in that case it would be better to just integrate JDunrar into Vuze.
Unless you are going to start a project for that integration, I would not expect any real torrent support in JD. There is just too much to do with JD as it is. Integrating the streaming portion of Vuze would just drown the team.
Maybe this example will get the point across. Windows tries to do everything on a huge assortment of hardware, without any need for the users to know anything about the OS. They have even integrated the web browser as the shell, so that they can get all of the neat HTML and STL effects. When Vista was released, there were over 1000 known bugs and 2000 other issues. That is part of the reason for automatic updates, Microsoft cannot keep up with the real world.
On the other hand, Mac OSX is very stable, has much fewer virus problems, and hardly ever crashes (compared to Windows). It is also several times faster on the same hardware. It doesn't try to do everything.
|