<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:dc="http://purl.org/dc/elements/1.1/">
  <channel>
    <title>DEV Community: Alessandro</title>
    <description>The latest articles on DEV Community by Alessandro (@alex75it).</description>
    <link>https://dev.to/alex75it</link>
    <image>
      <url>https://media2.dev.to/dynamic/image/width=90,height=90,fit=cover,gravity=auto,format=auto/https:%2F%2Fdev-to-uploads.s3.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F273447%2F4b3cbb75-44ab-4920-bd53-7b0b762fb707.jpeg</url>
      <title>DEV Community: Alessandro</title>
      <link>https://dev.to/alex75it</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/alex75it"/>
    <language>en</language>
    <item>
      <title>Answer: Design Pattern to model Request and Response Objects for Webservices</title>
      <dc:creator>Alessandro</dc:creator>
      <pubDate>Sun, 17 Nov 2019 10:37:12 +0000</pubDate>
      <link>https://dev.to/alex75it/answer-design-pattern-to-model-request-and-response-objects-for-webservices-2kcp</link>
      <guid>https://dev.to/alex75it/answer-design-pattern-to-model-request-and-response-objects-for-webservices-2kcp</guid>
      <description>&lt;div class="ltag__stackexchange--container"&gt;
  &lt;div class="ltag__stackexchange--title-container"&gt;
    
      &lt;div class="ltag__stackexchange--title"&gt;
        &lt;h1&gt;
          &lt;img src="https://res.cloudinary.com/practicaldev/image/fetch/s--pTF_nE4a--/c_limit%2Cf_auto%2Cfl_progressive%2Cq_auto%2Cw_880/https://practicaldev-herokuapp-com.freetls.fastly.net/assets/stackoverflow-logo-b42691ae545e4810b105ee957979a853a696085e67e43ee14c5699cf3e890fb4.svg" alt=""&gt;
            &lt;a href="https://stackoverflow.com/questions/26788608/design-pattern-to-model-request-and-response-objects-for-webservices/48450483#48450483" rel="noopener noreferrer"&gt;
              &lt;span class="title-flare"&gt;answer&lt;/span&gt; re:  Design Pattern to model Request and Response Objects for Webservices
            &lt;/a&gt;
        &lt;/h1&gt;
        &lt;div class="ltag__stackexchange--post-metadata"&gt;
          &lt;span&gt;Jan 25 '18&lt;/span&gt;
        &lt;/div&gt;
      &lt;/div&gt;
      &lt;a class="ltag__stackexchange--score-container" href="https://stackoverflow.com/questions/26788608/design-pattern-to-model-request-and-response-objects-for-webservices/48450483#48450483" rel="noopener noreferrer"&gt;
        &lt;img src="https://res.cloudinary.com/practicaldev/image/fetch/s--5MiFESHx--/c_limit%2Cf_auto%2Cfl_progressive%2Cq_auto%2Cw_880/https://practicaldev-herokuapp-com.freetls.fastly.net/assets/stackexchange-arrow-up-eff2e2849e67d156181d258e38802c0b57fa011f74164a7f97675ca3b6ab756b.svg" alt=""&gt;
        &lt;div class="ltag__stackexchange--score-number"&gt;
          44
        &lt;/div&gt;
        &lt;img src="https://res.cloudinary.com/practicaldev/image/fetch/s--Rk_a5QFN--/c_limit%2Cf_auto%2Cfl_progressive%2Cq_auto%2Cw_880/https://practicaldev-herokuapp-com.freetls.fastly.net/assets/stackexchange-arrow-down-4349fac0dd932d284fab7e4dd9846f19a3710558efde0d2dfd05897f3eeb9aba.svg" alt=""&gt;
      &lt;/a&gt;
    
  &lt;/div&gt;
  &lt;div class="ltag__stackexchange--body"&gt;
    
&lt;p&gt;The big problem I see in all the answers so far including the question is that they all violate the principal of separation of concerns, infomation hiding and encapsulation. In all answers request (and response) classes are tightly coupled to model classes. That is a more serious issue and raises…&lt;/p&gt;
    
  &lt;/div&gt;
  &lt;div class="ltag__stackexchange--btn--container"&gt;
    
      &lt;a href="https://stackoverflow.com/questions/26788608/design-pattern-to-model-request-and-response-objects-for-webservices/48450483#48450483" rel="noopener noreferrer"&gt;Open Full Answer&lt;/a&gt;
    
  &lt;/div&gt;
&lt;/div&gt;


</description>
    </item>
  </channel>
</rss>
