What is this 3000-4000 pixel count people keep writing about? That's about 100x30 - 100x40 pixels, which is about the same resolution as the info display on my DVD player. Am I missing something?
In Swedish it is du/ni. In the 40's or 50's people generally stopped using "ni", since it was considered a ramainder from the era of servants, giving a feeling of "I'm better than you" or something like that.
Nowadays, young people and immigrants have started using that term again, and it doesn't help that "ni" is more often used when referring to a group of people (so you start to wonder if the person is talking to you or to you and everyone behind you...).
IMHO, HTTP is a broken protocol, and the fact that sites can be Slashdotted proves it.
You're wrong. Sites being/. has nothing to do with the HTTP protocol. It's the servers (hardware/software/bandwidth - take your pick) not being able to cope with the extreme number of visitors.
I don't really see how a technique such as BT would improve on sites' availability. Most sites consist of rather small images and text files (HTML pages), and having to download a.torrent file or similar before downloading the content would just increase the volume needed to download from the server (this goes for the client too - even after downloading a.torrent file, it would still need to download the content, which includes all the overhead of HTTP headers and TCP/IP connections).
However, I do agree that the HTTP protocol could use some improvements...
Unfortunately, I can't seem to connect to the torrentse.cx tracker (or maybe I just misunderstood something about creating a.torrent file), I just get timeouts when trying to connect to the tracker.
Slashdot Mirror
What is this 3000-4000 pixel count people keep writing about? That's about 100x30 - 100x40 pixels, which is about the same resolution as the info display on my DVD player. Am I missing something?
In Swedish it is du/ni. In the 40's or 50's people generally stopped using "ni", since it was considered a ramainder from the era of servants, giving a feeling of "I'm better than you" or something like that.
Nowadays, young people and immigrants have started using that term again, and it doesn't help that "ni" is more often used when referring to a group of people (so you start to wonder if the person is talking to you or to you and everyone behind you...).
IMHO, HTTP is a broken protocol, and the fact that sites can be Slashdotted proves it. You're wrong. Sites being /. has nothing to do with the HTTP protocol. It's the servers (hardware/software/bandwidth - take your pick) not being able to cope with the extreme number of visitors.
I don't really see how a technique such as BT would improve on sites' availability. Most sites consist of rather small images and text files (HTML pages), and having to download a .torrent file or similar before downloading the content would just increase the volume needed to download from the server (this goes for the client too - even after downloading a .torrent file, it would still need to download the content, which includes all the overhead of HTTP headers and TCP/IP connections).
However, I do agree that the HTTP protocol could use some improvements...
Let's try this instead...
Unfortunately, I can't seem to connect to the torrentse.cx tracker (or maybe I just misunderstood something about creating a .torrent file), I just get timeouts when trying to connect to the tracker.
Any help would be greatly appreciated.
Sure. Here it is. :)
And since my outgoing bandwidth is limited, it would help if as many as possible could share this as soon as possible