Micah Cowan [EMAIL PROTECTED] writes:
Among other things, version.c is now generated rather than
parsed. Every time make all is run, which also means that make
all will always relink the wget binary, even if there haven't been
any changes.
I personally find that quite annoying. :-( I hope
Tony Godshall [EMAIL PROTECTED] writes:
available bandwidth and adjusts to that. The usefullness is in
trying to be unobtrusive to other users.
The problem is that Wget simply doesn't have enough information to be
unobtrusive. Currently available bandwidth can and does change as new
On 10/12/07, Tony Godshall [EMAIL PROTECTED] wrote:
Again, I do not claim to be unobtrusive. Merely to reduce
obtrusiveness. I do not and cannot claim to be making wget *nice*,
just nicER.
You can't deny that dialing back is nicer than not.
Personally, I think this is a great idea. But I
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Thomas Wolff wrote:
So I think it's clear the version thus produced was invoked.
Yeah, guess it couldn't be that easy! :)
Hm... well, can you verify that src/config.h has been correctly
generated to #define HAVE_SSL? If you go to src/ and type rm
Thomas Wolff wrote:
Hi,
as requested, I am sending you the output of configure and config.log
for checking the problem that my compiled wget does not retrieve
over https (Unsupported scheme).
Thomas, I don't see that anything went wrong at all with the
configuration. This makes me
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Hrvoje Niksic wrote:
Micah Cowan [EMAIL PROTECTED] writes:
Among other things, version.c is now generated rather than
parsed. Every time make all is run, which also means that make
all will always relink the wget binary, even if there haven't
On 10/12/07, Hrvoje Niksic [EMAIL PROTECTED] wrote:
Tony Godshall [EMAIL PROTECTED] writes:
available bandwidth and adjusts to that. The usefullness is in
trying to be unobtrusive to other users.
The problem is that Wget simply doesn't have enough information to be
unobtrusive.
On 10/12/07, Josh Williams [EMAIL PROTECTED] wrote:
On 10/12/07, Tony Godshall [EMAIL PROTECTED] wrote:
Again, I do not claim to be unobtrusive. Merely to reduce
obtrusiveness. I do not and cannot claim to be making wget *nice*,
just nicER.
You can't deny that dialing back is nicer
I don't want this to spiral down to Micah bashing. He has brought a lot
of good energy to the project, and gotten things moving forward nicely.
Thanks.
I know of instances where this option would be useful for me, and others
have chipped in. I think we all agree it isn't perfect and there is
no
...
I guess I'd like to see compile-time options so people could make a
tiny version for their embedded system, with most options and all
documentation stripped out, and a huge kitchen-sink all-the-bells
version and complete documentation for the power user version. I
don't think you
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Tony Godshall wrote:
[Jim]
Well, we need the plugin architecture anyway. There are some planned
features (JavaScript and MetaLink support being the main ones) that have
no business in Wget proper, as far as I'm concerned, but are inarguably
Tony Godshall [EMAIL PROTECTED] writes:
My point remains that the maximum initial rate (however you define
initial in a protocol as unreliable as TCP/IP) can and will be
wrong in a large number of cases, especially on shared connections.
Again, would an algorithm where the rate is
On 10/12/07, Hrvoje Niksic [EMAIL PROTECTED] wrote:
Personally I don't see the value in attempting to find out the
available bandwidth automatically. It seems too error prone, no
matter how much heuristics you add into it. --limit-rate works
because reading the data more slowly causes it to
13 matches
Mail list logo