Thanks for the link. Interesting stuff... except it looks more like a local solution.
While CARP is a wonderful piece of software and a worthy addition to any system administrator's arsenal, it's not a panacea. In some situations, you may be better off looking elsewhere. Fallover at different physical locations comes to mind immediately. CARP requires that the members of a group be on the same physical subnet. If you have systems spread across geographical distance -- or even on different subnets in the same datacenter -- it's probably best to look at other options for failover.
Both our hosts will be located at different geographical locations, in case there's a routing problem (West - East USA)