There selling the service of linking the domain name to an ip address. (or a DNS server anyhow).
I run my own DNS server, so they aren't selling
me that.
There not really selling a domain name, you can't take it away with you i.e. it's useless without a TLD entry.
I can take it to another provider.
A good analogy is that they are selling me
an easy to remember phone number, or perhaps
a listing in a very popular business directory.
If someone writes to the telephone company,
forging a letter saying that I want to give
up my 800-sex-com number, I have a good right
to be annoyed if the telephone company believes
the letter and doesn't even bother to make a
follow-up call to me.
I find that testing "code with side-effects" (ie: database inserts) is the hardest type of code to test, and I haven't yet found a solution that satisfies me.
One way to test these things which I've found worked
in the past was to put the whole test inside a
transaction, and roll back the transaction at the
end of the test.
Or rws
which let's you use C to write CGI scripts that are loaded into the server at run time (for extreme speed), and has database access, and hence is much more useful for dynamic webpages.
I moved to a complete whitelist solution about 3 years ago. Previously I used to use the "Bcc" method of filtering, but stopped doing that after a friend invited me to a party, and it accidentally got chucked in my (public) spam archive.
$ wc -l.whitelist 804.whitelist
It works, but it's a pain, and I still have to manually check the spam folder once in a while to catch people writing to me out of the blue about my software. And there are still a few false
positives in the archive (tell me about them, and I'll try and weed them out).
http://www.doc.ic.ac.uk/~phjk/BoundsChecking.html and http://web.inter.nl.net/hcc/Haj.Ten.Brugge/
Rich.
I run my own DNS server, so they aren't selling me that.
I can take it to another provider.
A good analogy is that they are selling me an easy to remember phone number, or perhaps a listing in a very popular business directory.
If someone writes to the telephone company, forging a letter saying that I want to give up my 800-sex-com number, I have a good right to be annoyed if the telephone company believes the letter and doesn't even bother to make a follow-up call to me.
Rich.
One way to test these things which I've found worked in the past was to put the whole test inside a transaction, and roll back the transaction at the end of the test.
Rich.Rich.
Rich.
Rich.
<plug>
Very true. That's why you need a web server like rws which is tiny, and loads C-based CGIs into memory, and has a full database layer.
</plug>
Rich.Rich.
Rich.
$ wc -l .whitelist .whitelist
804
It works, but it's a pain, and I still have to manually check the spam folder once in a while to catch people writing to me out of the blue about my software. And there are still a few false positives in the archive (tell me about them, and I'll try and weed them out).
Rich.
Gratuitous spam archive advert: http://www.annexia.org/spam/
Rich.
http://www.annexia.org/