# AWS vs REST and XML-RPC

**URL:** <https://www.ruby-forum.com/t/aws-vs-rest-and-xml-rpc/123670>\
**Category:** Rails\
**Created:** [December 19, 2007, 5:00pm UTC](https://www.ruby-forum.com/t/aws-vs-rest-and-xml-rpc/123670 "2007-12-19T17:00:56Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![matthew](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/m/ed655f/32.png) [@matthew](https://www.ruby-forum.com/u/matthew)\
**Post date:** [December 19, 2007, 5:00pm UTC](https://www.ruby-forum.com/t/aws-vs-rest-and-xml-rpc/123670/1 "2007-12-19T17:00:56Z")

</div>

Ok so DHH in the release post for Rails 2 talked about how there was  
clearly a side taken in the SOAP vs REST debate, and REST had one.

So what does that mean if one is wanting to create a small blogging  
engine with Rails 2, and want’s to use an external blogging  
application to connect with it?

Before it looked as if the Blogger API and MetaWeblog API were two  
ways of going about doing this through xml-rpc, but we are now  
“strongly” advised to move away from AWS.

I guess I’m not really clear on what to do, or what path to take. I’m  
positive I’m missing some crucial point here.