Comments on: A look at chatty vs chunky RESTful web services http://depts.washington.edu/ontheroa/?p=343 The UW blog for all things Resource Oriented Architecture & web services - email appdev@u.washington.edu Tue, 07 Feb 2012 00:23:05 +0000 hourly 1 http://wordpress.org/?v=3.0 By: Shawn Medero http://depts.washington.edu/ontheroa/?p=343&cpage=1#comment-163 Shawn Medero Wed, 24 Feb 2010 18:28:14 +0000 http://depts.washington.edu/ontheroa/?p=343#comment-163 Thanks for taking the time to write up how you've internally approached designing your services. One consideration when consider the chatty or chunky service design patterns is caching side-effects. In the past when I've designed chunkier responses I've gotten push back that clients want to be able to cache certain parts of the response more aggressively than others. Not suggesting it is an either/or problem, you can always offer both forms for different audiences. Just a cautionary warning. Thanks for taking the time to write up how you’ve internally approached designing your services.

One consideration when consider the chatty or chunky service design patterns is caching side-effects. In the past when I’ve designed chunkier responses I’ve gotten push back that clients want to be able to cache certain parts of the response more aggressively than others. Not suggesting it is an either/or problem, you can always offer both forms for different audiences. Just a cautionary warning.

]]>