As a first step to get something running, it's reasonable to put lots of logic into a controller method. But very soon, you end up wanting your controller methods to be "skinny".
I've used Spring very little. But my take is that, as with e.g. Jersey, a Spring controller is very much concerned with the HTTP protocol. That being the case, it seems like you'd like all your logic in a place that has almost nothing to do with the HTTP protocol. The benefit is that: 1. you can test that logic with plain old Java code—no need for an HTTP client 2. you can reuse that logic in non-HTTP contexts (other protocols, other situations) [ Full content available at: https://github.com/apache/geode/pull/3049 ] This message was relayed via gitbox.apache.org for [email protected]
