Hello Marc,
Tuesday, October 03, 2000, 3:31:09 AM, you wrote:
> Hello William,
> On Tue, 3 Oct 2000, William X. Walsh wrote:
>> This uses a database backend, and dynamically generates the
>> redirection and if cloaking is enabled the frames and meta tag info.
> Meaning that it uses more server resources...
Not really. The resources it uses are negligible.
>> And the nice part too, is that it can easily be setup so that
>> *.domain.com is redirected also, meaning anythinghereatall.domain.com
>> will work and redirect to the same place as www.domain.com and
>> domain.com.
> Useful only to catch those who make a typo in the first part of a URL...
Useful for people who want to get creative with how they link to their
sites too :)
> I do not doubt your perl code is very useful and saves a lot of *time*. I
> might come looking for it some day. For my setup or any small setup (in
> number of redirected domains) it would be overkill, I think.
Well, its not intended be a standalone redirection system. It is a
domain registry that bundles URL Redirection services for the domains
registered under it. I am using it to run a testbed 3rd level domain
registry right now, so the domains registered are in the form of
domainname.hmm.org (hmm.org is not the domain of the test bed, but it
will later be used with the software as another live registry), and
the user can have domainname.hmm.org delegated to their nameservers,
pointed to a static IP, or setup for URL redirection to the website of
their choice.
It really isn't a stand alone redirection setup, so yes, it would be
overkill, unless/until someone extracts just the URL redirection stuff
from it and wraps their own signup and management structure around it.
--
Best regards,
William mailto:[EMAIL PROTECTED]
