On Sat, 01 Feb 2014 17:46:53 +0100, Phil Haigh
<[email protected]> wrote:
Of course they’re going to call it REST if they think it is REST, in the
same way that many teams will say they are agile when they might only
implement a small sub-set of what being completely agile actually is.
The point is precisely naming. There are things that people should never
do (using the verbs without respecting their semantics), and there are
trade offs in REST that sometimes make sense (such as the cited versioning
in the URL, as it's browser friendly). The problem is that we call all of
that 'REST' and it makes confusion. In a better world a few different
"intermediate" practices would have been given different names.
--
Fabrizio Giudici - Java Architect @ Tidalwave s.a.s.
"We make Java work. Everywhere."
http://tidalwave.it/fabrizio/blog - [email protected]
--
You received this message because you are subscribed to the Google Groups "Java
Posse" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To post to this group, send email to [email protected].
Visit this group at http://groups.google.com/group/javaposse.
For more options, visit https://groups.google.com/groups/opt_out.
