When is REST not the right choice?
- On Sun, Aug 1, 2010 at 2:36 PM, Viswanath Durbha <viswanath.durbha@...> wrote:
In the space I work in, I don't know that I would use "not ideal" but would say that there are cases where the benefits of the style would not be taken advantage of. For example, when building internal apps where the you (or a small set of people) are in control of everything (clients, servers, intermediaries etc etc), then applying all the REST principles may not provide significant values and a RPC-based (or anything else) solution may work just fine.
- One broad way of thinking about an answer to this question is to look at protocols.
An alternate protocol probably suggests a different set of trade-offs with different characteristics for different situations:
Example: Mail - POP, SMTP, IMAP
Example: Instant messaging - Jabber, BEEP
Example: High-speed broadcast - UDP, JMS*, AMQP
* Yes, I realize that JMS, technically, is not a protocol, but it has been mapped onto several protocols, including AMQP.
On 08/01/2010 11:36 AM, Viswanath Durbha wrote: