Hash: SHA256

L Walsh wrote:
> Honest -- I hadn't read all the threads before my post...
> Great ideas Micah! :-)
> On the idea of 2 wgets -- there is a "clever" way to get
> by with 1.  Put the "optional" functionality into separate
> run-time loadable files.  SGI's Unix (and MS Windows) do this.
> The "small wget" then checks to see which libraries are
> "accessible" -- those that aren't simply mean the features
> for those libs are disabled.  In a way, it's like how
> 'vim' can optionally load perllib or python-lib at runtime
> (at least under windows) if they are present.  If they are
> not present, those features are disabled.  Too bad linux
> didn't take this route with its libraries (have asked,
> it is possible, but there's no "framework" for it, and
> that might need work as well.

I'm not sure what you mean about the linux thing; there are many
instances of runtime loadable modules on Linux. dlopen() and friends are
the standard way of doing this on any Unix kernel flavor.

Keeping a single Wget and using runtime libraries (which we were terming
"plugins") was actually the original concept (there's mention of this in
the first post of this thread, actually); the issue is that there are
core bits of functionality (such as the multi-stream support) that are
too intrinsic to separate into loadable modules, and that, to be done
properly (and with a minimum of maintenance commitment) would also
depend on other libraries (that is, doing asynchronous I/O wouldn't
technically require the use of other libraries, but it can be a lot of
work to do efficiently and portably across OSses, and there are already
Free libraries to do that for us).

- --
Micah J. Cowan
Programmer, musician, typesetting enthusiast, gamer...

Version: GnuPG v1.4.6 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org


Reply via email to