> Most applications with an API require a key (usually a unique and random > 16-26 character alphanumerical code) to confirm you are authorized to > access the account. I'm sure this key could be substituted by a username > and password (like twitterific for example). Once this native mobile app > is authorized to access the account it can do pretty much anything > someone on the website is allowed to do. Create, Remove, Update, and > Destroy (CRUD) operations and access some custom actions as well such as > adding friends.
Hi, yeah keys are one option. I'm using restful_authentication and I modified the plugin by adding some methods to handle the XML calls from the mobile. Regarding the keys I actually reused the cookie functionality of the same plugin, so for the mobile I set a long expiration for the cookie and the client can use the API for as long that is valid (logged in). I don't have the code here but I could post my changes here, I would maybe get some feedback about my approach as well :-) As Billee D. mentioned adding the XML response featyre to the rails app is very simple and JSON is also a possibility. I think it also depends on what is easier to parse and consume for you on the terminal side. Cheers. -- Posted via http://www.ruby-forum.com/. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Ruby on Rails: Talk" group. To post to this group, send email to rubyonrails-talk@googlegroups.com To unsubscribe from this group, send email to rubyonrails-talk+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/rubyonrails-talk?hl=en -~----------~----~----~----~------~----~------~--~---
