Etora lets you write readable, maintainable table definitions and automates much of the redundant work involved in creating tables. It reads a file of database table definitions and outputs the Oracle SQL to create or drop the tables and associated objects. All constraints, sequences, and triggers are intelligently named, which aids in interpetation of Oracle error messages. An Etora file can be roughly 1/3 the size of the equivalent SQL and consequently easier to read and maintain.
IPShutter lets you firewall off ports such as ssh, and selectively enable access with a one-time password. For example, if you want to log into the server from a friend's house, you pull out a list of one-time passwords and point the Web browser at a URL that contains one password. That tells the server to allow ssh connections from your friend's IP address for five minutes. Connections made in that period will stay up indefinitely.
Libfastcounters is a C library to maintain counters. It makes it convenient for a server program to count many kinds of events. Incrementing is fast, on the order of nanoseconds. Incrementing is atomic. Counters are shared across processes. Counters are persistent. You can address counters by number or by name. Libfastcounters includes a command line tool to create, modify, and read the persistent counters file.
ASP != webmail
The focus of ASPs will be delivering enterprise applications. Here's the basic idea: Let's say you're creating a high-traffic web site. You'd like to use Oracle for the database, but it's pretty expensive. To put Oracle on a 400 Mhz Pentium III will cost $40,000. For the first several months your site could be handled by MySQL. But you want to code for Oracle from day 1 so there is no discontinuity.
What happens if you put Oracle on a very low-powered machine? You could save money on the license, but your site won't handle load spikes. Remember, when the db starts piling up connections, the entire site jams.
Now imagine that Joe is an ASP. He got some VC's to buy a huge Sun server with redundant everything and put Oracle on it. He has huge bandwidth to the internet. You sign an agreement with Joe to pay him a monthly fee for a certain amount of transfer and storage. Joe worries about backups, raid, hardware and s/w upgrades, etc. By the way, you also want really good DBA's - but not enough to hire them full time. What you really want is to punch a button on your speed dial and say, "Why does this SELECT take so long?" and hear "OK, I created an index on column FOO, it should be much faster now."
Anyhow, I don't blame you for the confusion. I'm not sure how this meme got started that says ASP's would sell to consumers. The types of applications that could benefit from ASP are the monstrously big, expensive applications whose unit deployment cost flattens out beyond a certain volume.
Expect the same kind of relationship you'd have with a colocation or hosting vendor. They will sometimes screw up, but they'll have to make it good in the long run. Your experience with Yahoo is altogether different, as you were not a paying customer at all, much less a substantial business account.