Edit - Software Engineering Stack Exchange

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

As with all programming approaches, there's not one size fits all otherwise we'd not debate and discuss different patterns and approaches in every applciation we build, we'd just always use the same things. DTOs are essentially just POPOs they're just named to show some intent. There's nothing with using a DTO to "transfer data" between eg service, controller, and into view. There's nothing in the name or structure of the classes that indicate or limit from where and to data is transferred

James
– James

2019-10-17 08:34:32 +00:00
Commented Oct 17, 2019 at 8:34

Add a comment |

Correct minor typos or mistakes
Clarify meaning without changing it
Add related resources or links
Always respect the author’s intent
Don’t use edits to reply to the author

create code fences with backticks ` or tildes ~
```
like so
```
add language identifier to highlight code
```python
def function(foo):
print(foo)
```
put returns between paragraphs
for linebreak add 2 spaces at end
_italic_ or **bold**
indent code by 4 spaces
backtick escapes `like _so_`
quote by placing > at start of line
to make links (use https whenever possible)

<https://example.com>

[example](https://example.com)

<a href="https://example.com">example</a>

formatting help »
answering help »