Long-Awaited BitTorrent 4.0 Released

wintermute1974 writes "After sitting at a stable release of 3.4.2 since last spring, Bram Cohen's official BitTorrent client has been upgraded to version 4. In addition to its existing, rock-steady functionality, BitTorrent now sports a new queue-based UI. The revision details are on the BitTorrent site. Packets are now marked as bulk data too, which is significant considering that about a third of all Internet traffic is currently torrent data."

Comments

Good to see progress...

[ratsnapple tea]

The OS X client is still at 3.4.2. Is anyone working on an update? (I'd offer to help, but I don't program :p)

Re:Good to see progress...

[Coryoth]

The OS X client is still at 3.4.2. Is anyone working on an update? (I'd offer to help, but I don't program :p)

It's in python so you should be able to just grab the source and use btdownloadcurses.py in Terminal.app (or whatever it is). Do you need a pretty GUI, or do you just want the new functionality etc.?

Jedidiah.

Re:Good to see progress...

[rsmith-mac]

Do you need a pretty GUI, or do you just want the new functionality etc.?

In all seriousness, it's a Mac. The userbase is not going to accept an application that doesn't have a "pretty GUI" because the GUI is much of what the platform is about. Just see OpenOffice for an example of software that's underutilized for its lack of an effective Mac GUI.

The 'bulk data' tag

[Raindance]

Since it's a decentralized standard, we'll need other clients to mark packets as 'bulk data' as well to get full benefits in routing from this. Since companies are starting to use BT commonly to distribute files in-game (or will, shortly), their code will need to be updated too. So, no magic bullet but a step in the direction of creating a heirarchy of data packets.

I'm interested to see where this'll go-- will ISPs absolutely choke 'bulk data' packets and drive folks into using older or fringe BT clients to get faster downloads? Will this help solve VoIP realtime bandwidth issues? Will the 'good net citizen' vibe surrounding writing the 'bulk data' flag into ones code overshadow potentially making ones users into second-class net citizens?

Or will this not be a big deal at all?

Probably some of everything, I suppose.

Re:The 'bulk data' tag

[ip_fired]

I'm interested to see where this'll go-- will ISPs absolutely choke 'bulk data' packets and drive folks into using older or fringe BT clients to get faster downloads?

I don't think they'll choke "bulk data", because many other protocols mark their data bulk as well (ftp being one of them, if you have a modern client).

It is very helpful to ISPs to have the bulk classification, so that their more time-sensitive data (ie, VOIP) doesn't get clobbered when someone starts using bittorrent.

It's not like it's difficult to choke bittorrent traffic anyway, just look for communication on ports 6881 to 6888.

If they do, it'll just make everyone remove the bulk flag, and then there will be no easy quality of service queing.

Irony.

[DarkHelmet]

http://www.bittorrent.com/index.html

Is it just me... but does anyone else find it ironic that there isn't a torrent available for downloading Bittorrent?

Re:Irony.

[cdsr]

would you like to download winzip.zip too?

Great! I Love BitTorrent.

[Murdock037]

Because I hate going to the theater to see... uh, Linux binaries.

bulk data

[vespazzari]

is bulk data what fat chick pr0n is being referred to nowdays?

ABC

[Anonymous Coward]

has had a far better interface and featureset for years.

Bulk data?

[IntellectualCritic]

Packets are now marked as bulk data too

Can somebody explain what that means?

I'm assuming that's not like bulk mail over the internet. I'd hate to accidently download viagra when I just when a torrent file.

Re:Bulk data?

[Anonymous Coward]

Let's look at a few options vis-a-vis protocols that make use of TCP-IP. You have, for example Voice over IP (VoIP); Hypertext Transfer Protocol (HTTP); File Transfer Protocol (FTP); Network News Transfer Protocol (NNTP); Simple Mail Transfer Protocol (SMTP); Internet Relay Chat (IRC); and Secure Shell (SSH). (This list is not complete, but it's for illustrating the point, not to list every damn protocol on the whole Internet.)

Now, taking these one at a time. VoIP has certain needs: it needs a certain amount of bandwidth, and its data must be transferred within a short period of time, or it becomes unusable. A VoIP connection is generally held for of the order of minutes, so quick setup of a connection is not a high priority. HTTP needs quick setup/teardown, because you have one connection for each file (typically kilobytes in size; yes, I know that later versions of HTTP can transfer multiple files within one connection), but latency is not a huge concern; bandwidth might be, depending on the data. FTP is an interesting beast: low latency and low bandwidth for commands, but high bandwidth and don't-care latency for data. Setup/teardown times not a major issue. NNTP needs high bandwidth, but latency is not a concern at all. SMTP usually needs low bandwidth, and latency isn't a major issue, as long as the message gets through. SSH needs low latency, but bandwidth needs are generally low.

You have a relatively small pipe to the rest of the Internet. There are high demands on this pipe. How do you decide what gets pushed through, and what gets dropped, or delayed until later?

BitTorrent marking its packets as bulk means that quality of service systems can say "These packets aren't of major importance; they can be deferred until later". So the short-term throughput of BT is reduced, for the benefit of others who need the pipe for applications like VoIP (for example). When those other applications reduce their demands, BT is able to transfer its data.

The understanding is simple: the urgency in the transfer of data via bittorrent is low, so if bandwidth is at a premium, the routers can drop, or throttle, the bittorrent data to make room for high priority data. It's the same principle as FedEx uses: if you have stuff that needs to be moved FAST, you pay a price premium, and it gets moved on the next plane, bumping off some low-urgency, low-price cargo to the plane afterwards. If there's a lot of high priority and low priority traffic, such that the low priority traffic is building up faster than it can be moved, it's time for FedEx to buy more planes, or start not accepting low priority traffic -- or, in the ISP business, to buy a fatter pipe.

Hope this helps.

Marking Packets Correctly

[Red Pointy Tail]

I hope packets are also marked with the evil bit too, which is significant considering that most of all Torrent traffic is currently evil data.

Re:yep

[commodoresloat]

why bother with Firefox when we've got Safari?

You misspelled "Camino".

Initial impressions...

[Rexz]

Installer doesn't give any indication it's installing until you get a "Finished!" box. No choosing paths, no status indicator, nuffin.

Two donation nag screens.

Steals .torrent file associations.

No scraping the server for total seeder/peer numbers.

No moving completed downloads. No advanced seeding rules. No selecting of individual within a torrent. No download speed capping.

25mb memory usage running just one torrent.

Nothing excites me about this client. I look forward to its apparent efficiency increases being incorporated into Azureus et al, though.

Who cares?

[Anonymous Coward]

The official client has been miles behind most of the unofficial ones, and as far as I know nobody with any sense uses it anymore. And as far as I can see, this new version only makes it slightly less inferior. So why does it matter that it's been released? For that matter, why was it even made?

I don't see the point in reinventing the wheel as far as clients go when there are far better alternatives already out there. Let other people write the clients, and concentrate on improving the protocol.

Re:Link and Changelog

[NuclearDog]

I'll translate the preamble to English...

• The BitTorrent client and updates/etc are all covered under this license.
  
• The license is considered a valid open source license.
  
• You can give it (the software) away just by itself or on a cd/in a zip with multiple other programs. You don't have to pay royalties.
  
• You have access to the source & binaries.
  
• You can modify the source & fork the program.
  
• Any modifications made to the program have to be licensed under this same license.
  
• Use it however you want, but there is no warranty provided.
  
• If you sublicense the code, you can charge for warranty/support or for offering indemnity for your customers, but the source must remain free.
  
• If you file a patent claim against the BitTorrent software, you lose all rights under the license (right to re-distribute, etc.)
  
• You can re-license any works you create based on the code, but you have to license it under an OSI-approved license that is compatible with this license.
  

(Note: This may not be 100% accurate, IANAL, I am not responsible, etc, etc.)

Re:Azureus rocks...

[Anonymous Coward]

Unfortunately BitTornado runs in Python, which can get almost as slow as client-side Java when you have a lot of stuff running. I'd recommend the pure C++ BitComet.

Re:Hmm

[stratjakt]

eXeem is a sloppy piece of crap, and a thinly veiled vehicle to get spyware and malware on your system (whse).

Slashdot staff should be ashamed to have promoted it like they did. They did 2 or 3 articles about it, as if it were some great tech sent from the heavens.

Besides the fact that the very notion of it is what's wrong with the internet, and why the government will eventually regulate the hell out of it. The entire point is to trade warez. I did an eXeem search for linux, and didn't get one result - so don't give me some bullshit about slackware isos. Society are like kindergarteners, they had a little freedom, and blew it. Now we're all going to be grounded.

Actually, is that why michael left? It wasn't long after he "wrote" a couple "eXeem is great! get your warez on eXeem!" articles that he left.