...anyone else have any thoughts on that method?
Take a look at my comments in this 2008 discussion, in which I suggest using a 302, essentially what HuskyPup is suggesting... Moving to a New Domain - Official Advice from Google http://www.webmasterworld.com/google/3629305.htm
While I still haven't tried it myself, I've come to feel that if the client isn't looking for a big flashy rebranding premiere of the new domain, you should use a 302 for a while, gradually build a reputation on the new domain, and then follow that up and change the 302 to a 301.
The logic of this is that while you'd normally want to avoid a 302, because it would show the site on both domains and potentially split your link vote, in this case that would be fine. During the 302 period you should try to build some natural links to the new domain, and if you get some inbounds to the current (old) domain, that won't hurt because, in this case, everything will eventually get redirected to the new domain.
Note, btw, that I'm extremely adamant about keeping control of the old domain more or less forever. Once you've done the 301 and pointed your old domain to the new IP using your A-records on your DNS and added the necessary code to your .htaccess, you can probably take the old site down in a week or so. The important thing is to have both sites operating simultaneously during DNS propagation.
But six months is not nearly enough, IMO, to keep the old domain pointing at the new hosting space. In part, it may depend on your business model and the kind of reputation you've built up for the old domain. Again, I suggest "in perpetuity and beyond".