Hi I have a question regarding using Rails as a REST web service. I understand the concept and have implemented it into a project. As far as I''m logged in into the application, I can pull out data in any format that is specified in the application. But lets say that I want to use it as a service. How do I pull the data out? When you use SOAP / WSDL, you send your request in xml format together with authentication data (login/pass), but how does this work in Rails? In my application, when a user is logged in, his user data gets stored in a session. But when you speak with the application through lets say a script, I need to send my login data that needs to be verified, but no session will be created. I hope someone can help me in the right direction. Thank you in advance -- 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-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org To unsubscribe from this group, send email to rubyonrails-talk+unsubscribe-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org For more options, visit this group at http://groups.google.com/group/rubyonrails-talk?hl=en -~----------~----~----~----~------~----~------~--~---
> But lets say that I want to use it as a service. How do I pull the data > out? When you use SOAP / WSDL, you send your request in xml format > together with authentication data (login/pass), but how does this work > in Rails?I think most people are using HTTP Basic Authentication for their REST web services in Rails. Run this over SSL if you want the transmission to be secure. Yes, it''s not as extensive and flexible as SOAP and WS-* (deathstar), but that''s exactly the point. I''ve done some pretty extensive work with WS-* due to having to integrate with services using it. But, even in these cases they really aren''t depending on any more security than that provided by the standard web technologies. Just because you provide extensive flexibility doesn''t mean that people will use it, or even need or want it. Also, I believe that ActiveResource (and other plugins) pretty much take care of handing authentication through HTTP Basic Authentication for you. Read up on ActiveResource and see if that helps clear things up a bit for you. -- 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-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org To unsubscribe from this group, send email to rubyonrails-talk+unsubscribe-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org For more options, visit this group at http://groups.google.com/group/rubyonrails-talk?hl=en -~----------~----~----~----~------~----~------~--~---