Hannes, Twilio's API is our product. Whatever we chose for cryptographic signing and message serialization would have to be something that our users can understand quickly and easily. In many cases, these users will have little to no experience with some of these technologies. JWT is the closest thing to satisfying our test of simplicity.
-jeff On Thu, Feb 24, 2011 at 5:17 AM, Hannes Tschofenig < hannes.tschofe...@gmx.net> wrote: > Hey Axel, Hi Jeff, > > looking at your post regarding the JWT implementation I was wondering about > one aspect: You are providing an implementation in Java, Python, PHP, and > Ruby. > > Why didn't you implement a sub-set of the CMS implementation for signing > instead? Maybe you could have used existing libraries already. > > Ciao > Hannes > >
_______________________________________________ OAuth mailing list OAuth@ietf.org https://www.ietf.org/mailman/listinfo/oauth
