Unless I'm missing something you only need to have a version Apache that supports SNI then have NameVirtualHost for your https port. If your os/distro doesn't make that version easily available then I can see how it might take extra work to get SNI support.
What I should have said was that I've been too lazy (like to an extreme degree) to host multiple SSL sites using SNI. Just buying another IP was easier for me. It's probably stupid to do that but that's just me.
Actually doing SNI can be the stupid solution. We still have a large number of customers on Windows XP and we probably will for years to come. SNI isn't supported on any IE browser running on XP, so you need to buy the extra IPs anyway.
