like I said before you have these representations and you're transferring them over the web to other people and the state part comes from viewing interactions ??? like a state machine or the fact that it is a stateless protocol it has that sort of double sort of meaning but you can just tell by looking at the name of those three style that they are all intended for very different purposes and therefore they're all good at very different things and so, it 's really important as developers when we're building tools for other developers to use that we build them with the right end goal in mind so, if you want to share methods : use RPC if you want to share objects, think about using RPC instead of SOAP because it's terrible [laughs] just go back to using RPC but, if you want something else think about using actual REST so, like I said it's not about exposing you objects over the web and this is something that ends up happening with Ruby on Rails, specifically what Rails has done has been an amazing and terrible thing for REST in an abstract sense because 