> This has occasionally led us to keeping more than may be desired in a more > general resource, for example say /customer/45 with a lot of data, rather > than /customer/45, /customer/45/billingaddresses, /address/1, /address/2, > /address/378 as separate resources, incurring 1+n calls to the server, 1+n > transactions/auth checks etc.
But don't you OTOH find it rather easy to add caching so that the chattyness is isolated at the HTTP level, rather than reaching the backend? Spreading short-lived self-populating caches at strategic places seems to make all the difference with REST architectures. -- You received this message because you are subscribed to the Google Groups "The Java Posse" group. To post to this group, send email to javapo...@googlegroups.com. To unsubscribe from this group, send email to javaposse+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/javaposse?hl=en.
