Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

[fouleggs] Introduce own message types replacing DefaultMessagingProtocol #109

Open
CodeLionX opened this issue Aug 2, 2018 · 0 comments
Open

[fouleggs] Introduce own message types replacing DefaultMessagingProtocol #109

CodeLionX opened this issue Aug 2, 2018 · 0 comments
Labels
Codacy - Style Nice-To-Have

Comments

@CodeLionX
Copy link
Owner

Issue

The fouleggs sample application makes use of the DefaultMessagingProtocol, which should only be used for testing and debugging purposes.

Problem Description

DefaultMessagingProtocol should only be used for testing and debugging purposes, because it does not model domain logic and introduces tight coupling. Our sample applications should show best practices.

Supporting Information

See PR #105 review and comments.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
Codacy - Style Nice-To-Have
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@CodeLionX