> However, I think the real reason that REST hasn't been adopted fully is that service providers like Dropbox have found that there advantages to binding client

> However, I think the real reason that REST hasn't been adopted fully is that service providers like Dropbox have found that there advantages to binding client developers to their hardcoded APIs; the last thing Dropbox wants (and what REST would provide) is a standardised set of media-types and RFCs describing the interactions for a standardised way of interacting with an external cloud-based storage provider. I'd argue it's not a problem if a vendor can generate clients for his API. I'd also argue that most clients break with each API version anyway, because of the way developers code them.