When I looked at the release notes sent out by email, I saw this under "New functionality": "httpd(8) can now serve files larger than 2GB in size." I'm very surprised by this.
apache has been able to do that since 2.2. Of course, a web page larger than 2 gigs is a bug not a feature...
Large File Support
httpd is now built with support for files larger than 2GB on modern 32-bit Unix systems. Support for handling >2GB request bodies has also been added.
apache has been able to do that since 2.2. Of course, a web page larger than 2 gigs is a bug not a feature...
You *are* aware that HTTP is used to transfer more than just HTML, right?
Like he said, it's a bug not a feature. Torrent and FTP are much more efficient, especially when handling interrupted transfers. HTTP doesn't. Unreliable networks can make a net-based installation process drag on and on or even freeze.
Torrent and FTP are much more efficient, especially when handling interrupted transfers.
Bullshit. Bittorrent isn't appropriate for all applications, and for large transfers, HTTP and FTP are basically a wash as far as efficiency goes, while HTTP handles resumes just fine (the browser needs only to send along a start offset in the request header). Meanwhile, unlike HTTP, FTP doesn't play well with firewalls or caches.
The web server can finally serve large files (Score:3, Interesting)
When I looked at the release notes sent out by email, I saw this under "New functionality":
"httpd(8) can now serve files larger than 2GB in size."
I'm very surprised by this.
Re: (Score:2)
When I looked at the release notes sent out by email, I saw this under "New functionality":
"httpd(8) can now serve files larger than 2GB in size."
I'm very surprised by this.
apache has been able to do that since 2.2. Of course, a web page larger than 2 gigs is a bug not a feature...
http://httpd.apache.org/docs/2.2/new_features_2_2.html [apache.org]
Large File Support
httpd is now built with support for files larger than 2GB on modern 32-bit Unix systems. Support for handling >2GB request bodies has also been added.
Re: (Score:2)
apache has been able to do that since 2.2. Of course, a web page larger than 2 gigs is a bug not a feature...
You *are* aware that HTTP is used to transfer more than just HTML, right?
Re: (Score:2)
apache has been able to do that since 2.2. Of course, a web page larger than 2 gigs is a bug not a feature...
You *are* aware that HTTP is used to transfer more than just HTML, right?
Like he said, it's a bug not a feature. Torrent and FTP are much more efficient, especially when handling interrupted transfers. HTTP doesn't. Unreliable networks can make a net-based installation process drag on and on or even freeze.
Re:The web server can finally serve large files (Score:2)
Torrent and FTP are much more efficient, especially when handling interrupted transfers.
Bullshit. Bittorrent isn't appropriate for all applications, and for large transfers, HTTP and FTP are basically a wash as far as efficiency goes, while HTTP handles resumes just fine (the browser needs only to send along a start offset in the request header). Meanwhile, unlike HTTP, FTP doesn't play well with firewalls or caches.