I have seen a few samples of SRP protocol used for web applications and I wonder why nobody ever uses it for RESTful authentication. I have done some research and I couldn't find any single example, not even one. SRP together with password hashing functions such as bcrypt, scrypt or pbkdf2 seems pretty solid to me, but it seems like nobody has tried it before which is odd. Am I missing something here that is conceptually contradictory? Does SRP protocol somehow remove RESTfulness?
Much of the adoption of technology is dependent on economics, and SRP is no exception. Software shops are generally not going to spend or money on a specific technology which does not provide any sort of novel benefit. For example, the benefit SRP would provide to an organization would be that they do not have to store passwords in their system. OpenID already fulfills a similar role. Choosing SRP means that an organization will have to incur the costs of developing the implementation, accept the risks of not implementing it correctly, and would provide no additional benefit over the cheaper method (OpenID, etc.)
SRP does not violate RESTful practices, as far as I'm aware.