Archive for September, 2009

Support the VRF

They want to send a team into Cambodia to document great artists and musicians. It sounds like a pretty amazing project. They just got my $20.

ATTs 1993 Predictions Remarkably Accurate

h/t core77.com
It’s amazing how many of these 1993 predictions are just common place today.

Seth Godin lists the questions to ask before building a website

Seth’s Blog: Things to ask before you redo your website
I think these are perhaps the tenth and eleventh questions you should ask, not the first two. Here’s my list of difficult and important questions you have to answer before you spend a nickel:

CouchDb: Replication halts between two databases and results in a hung erlang process

We were seeing a json error in the couchdb logs. Apparently 0.9.1 (because of MochiWeb) doesn’t like certain UTF characters. Unfortunately, this causes replication to totally hang. That’s a bummer. It looks like it’s been patched:
http://issues.apache.org/jira/browse/COUCHDB-333
However, that’s not in the 0.9.1 release.

Confused about CouchDB changes API?

If the couchdb book confused you regarding the changes api that supposedly exists:
http://books.couchdb.org/relax/reference/change-notifications
I think that’s a 0.10 release feature (and not yet in 0.9.1). I stumbled upon this API which seems to do something very similar: http://wiki.apache.org/couchdb/HTTP_Document_API?action=show&redirect=HttpDocumentApi (scroll down to “all_docs_by_seq”).

Avoding the “Dog pile” effect

How to avoid the dog-pile effect on your Rails app | Plataforma Blog
Imagine that in a certain hour, this page on your application receives 4 requests per second on average. In this case, between the first request and the query results being returned, 5 seconds will pass and something around 20 requests will hit your […]

Fix string memory leaks in Ruby 1.8.6

UPDATE: This is rails-incompatible... which sucks.
Ruby 1.8.6 leaks memory in some surprising places. Even gsub and split on the String class cause some bad headaches. If you're using Haml and 1.8.6 - you are probably in a bit of trouble.
Read more: http://blog.edhickey.com/2008/12/03/memory-leak-in-ruby-186-string-class/
However, simply overwriting the offending methods fixes this memory leak at least. [...]