🚀 go-pugleaf

My initial thought of 'depth=n' was simplistic.  Now I
feel that the software should be able to respond to
commands like:

        Go grab that file.
        Go grab the whole of that site.
        Go grab that page and its immediate links.
        Go grab... but just the html.
        Go.. but just the html and piccies (no .zips etc)
        Grab the off-site links, just to the 1st level.
        etc

Phew!  In essence I think it boils down to six
different depth parameters, factored into
offsite/onsite, and html/images/other.

So I end up with either 6 different depth keywords,
or e.g. depth=1,2,3,4,5,6.  Either way, yuck.

        ------------------------------------

As for how to browse all these good files offline,
and the inelegance of browser-specific solutions,
how about this:

A proxy.  You go into your browser, set the proxy
as //yournodename.demon.co.uk:8080 and start surfing.
Your proxy doesn't talk to the outside world, so
it can't (first time) satisfy your request(s).  But
it writes a file for ka9q.

You then go online and the files are fetched.  Offline,
restart the browser and now the proxy has what you
want.  The difference between this and a cache is
that it's a read-ahead cache, controlled by the
six depth settings described above.

One problem is it needs multitasking, so if you don't
browse under Windows (or Desqview?) then you're stuffed.

Will it fly?

--
John Washington