Link_Controller

 view release on metacpan or  search on metacpan

TODO  view on Meta::CPAN

	Our indexes of links to and from objects should be updated
	gradually 

I couldn't do that in the design becuase when I started using DBMs for
the index databases they turned out to be many megabytes, several
times larger than the CDB files and so unmanagable.

At the time I started writing this, none of the free SQL databases
could satisfy the needs of this project.  Now they've improved
considerably. It would be nice to have an implementation of the Link
class which was overlayed over SQL storage.

Some of the techniques used in this set of programs seem a little
brutal (e.g. the fixlink program doesn't really understand html and
just guesses where to make substitutions..).  Comparative testing
against other programs would be nice.

Overlay links

It might be nice if people could keep personal information about links
in their own database.  For example, someone might have a link which
only exists for six months a year and want to record that it should
only be worried about at that time.  This would be kept in a DB file
as hashes which were then overlayed over the original Link, but
otherwise treated the same.

Possibly give extract-links a robot agent option in case someone wants
to use it for downloading from the www.  I'm not sure if this is
encouraging people to do things they shouldn't do or is something that
should be provided because otherwise people will use it without the
option.

REGRESSION TESTS



( run in 1.020 second using v1.01-cache-2.11-cpan-49f99fa48dc )