3 ms·
A HTTP request is a function call. A function call is message passing. No matter if you use RPC, SOAP or what not. It's conceptually all the same - the caller s
by danbruc 13y ago
A HTTP request is a function call. A function call is message passing. No matter if you use RPC, SOAP or what not. It's conceptually all the same - the caller sends a message to the callee which responds with another message.
- steveklabnik 13y agoYes, if you map the concepts over. Which is what you just did. The RESTful architecture is explicitly _not_about function calls. It's about manipulating state diagrams. Yes, you do that through a message, but it's different than a function call, unless you define 'function' and 'message' in a way that's completely meaningless. If any message is a function call, a UDP packet is a function call.
- alphadogg 13y agoWaitaminute. Anything that transforms ("manipulates") state is a function call. It's y = f(x), where f() is a GET, PUT, POST, etc, x is the resource and y is the response, no? REST is about function calls, but instead of emphasizing the function, it emphasizes the resource and standardizes the functions you can use.
- bct 13y agoalphadogg, you have been hellbanned for more than 2 years.
- mcguire 13y agoAt this point, I'd just like to inject that looking anything across a network as a function call is probably not a good idea.