Marnen Laibow-Koser wrote in post #969564: > Agreed that SOAP is less convenient that REST, but why do you think > Rails can't provide it well?
I'm just saying that if SOAP is the only thing the app is doing, why not use a framework that has SOAP support built-in. >> I'd say, do yourself a favor and either use Rails as it is intended, >> which is to provide web services through REST. Or find a framework you >> won't have to fight against every step of the way. > > What would have to be fought against? This doesn't appear to make > sense. I'll reiterate that this is my opinion. This will remain my opinion until someone can point to a plugin/gem that proves that SOAP is easy and robust with Rails. I'll concede my opinion if someone can do that. There are other frameworks that have more robust SOAP support built-in. Obviously, since Rails provides no built-in support for it. So if that's the only deciding factor in choosing a framework, why choose one that is inherently opposed to your apps needs? I'm not at all saying that it is impossible to provide SOAP services with Rails. Besides my experience with SOAP has never been a pleasant one. My opinion is already stacked heavily against it. -- 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 [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/rubyonrails-talk?hl=en.
