Yep that makes sense about transactions having confirmations not addresses
To be able to use gettransaction I need to have a transaction id which is not something I automatically have for a deposit, only for a send.
I can get a list of incoming transaction ids using
bitcoind listtransactions ACCOUNT
however I still have the problem of having to do lots of filtering if ACCOUNT has a lot of transactions. I guess I could keep track of how many transactions were returned the last time I called it and use that in the 'from' parameter to narrow down the list.
Thanks for the ideas. Still doesn't seem like a neat solution, but listtransactions is better than the previous ideas I had.
I might clarify the reason I made this title 'address confirmations' and not 'transaction confirmations' is that I plan to have each address used only once, and hence address should
be analogous to a transaction. Of course I cannot assume that the address will indeed only be used once since someone may pay to it multiple times, so I am also thinking about how to deal with that scenario should it arise.