title: @ModelAttribute vs @RequestBody, @ResponseBody
body: <p>@ModelAttribute</p>
  
  <pre><code>RequestMapping(value="/owners/{ownerId}/pets/{petId}/edit", method = 
  RequestMethod.POST)
  public String processSubmit(@ModelAttribute Pet pet) { }
  
  http://.../?name=Something&amp;age=100
  public String doSomething(@ModelAttribute User user) { }
  </code></pre>
  
  <p>@RequestBody</p>
  
  <pre><code>@RequestMapping(value = "/user/savecontact", method = RequestMethod.POST
  public String saveContact(@RequestBody Contact contact){ }
  
  { "name": "Something", "age": "100" } in request body
  public String doSomething(@RequestBodyUser user) { }
  </code></pre>
  
  <p>@ModelAttribute will take a query string. so, all the data are being pass to the server through the url</p>
  
  <p>@RequestBody, all the data will be pass to the server through a full JSON body</p>
  
  <ol>
  <li>Now which one is the best approach ??? </li>
  <li>If both are for same purpose to bind to the bean..which one is the best practice or widely used as standard practice? </li>
  <li><p>Both handles multi-part file and does it both have equivalent options with one another ?
  <a href="https://javabeat.net/spring-multipart-file-upload/" rel="nofollow noreferrer">https://javabeat.net/spring-multipart-file-upload/</a>
  <a href="https://stackoverflow.com/questions/14615692/how-do-i-upload-stream-large-images-using-spring-3-2-spring-mvc-in-a-restful-way">How do i upload/stream large images using Spring 3.2 spring-mvc in a restful way</a></p></li>
  <li><p>Does any one of them has lesser capabilities then the other one? Like length limitations, method limitations. Drawbacks</p></li>
  <li>Which one is more secured in terms of security ?</li>
  </ol>