Niclas Hedhman wrote: > I found the article; > http://www.infoq.com/articles/webber-rest-workflow > rather informative. I am especially fond of > > <quote> > The key to successful evolution is for consumers of the service to > anticipate change by default. Instead of binding directly to resources > (e.g. via URI templates), at each step the service provides URIs to > named resources with which the consumer can interact. > </quote>
Yup, I think that this is one of the most important articles published this year. Many of the architects I've talked to recently is starting to realize that "ESB in the middle" and WS-* intensive architectures is not the way to go, but the inevitable followup is "so what then?", which this article begins to answer quite nicely. /Rickard _______________________________________________ qi4j-dev mailing list [email protected] http://lists.ops4j.org/mailman/listinfo/qi4j-dev
