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

Better separation of concerns with (api &) cqrs-api #44

Open
ikitommi opened this issue Jul 1, 2016 · 0 comments
Open

Better separation of concerns with (api &) cqrs-api #44

ikitommi opened this issue Jul 1, 2016 · 0 comments
Labels
enhancement

Comments

@ikitommi
Copy link
Member

ikitommi commented Jul 1, 2016

  • handlers should return non-ring responses
  • naked values or success denoting success
  • success, failure and error are Records, translated into ring-respones in the leave-pipeline
  • extra interceptor to throw failure and errors => easy to invoke apis directly with dispatcher
  • Ring-spesific things can be tagged as type :kekkonen.ring/handler, returning raw ring respones

Why?

  • Separation on concers, returning a ring response from web socket -handler is lame
  • Easier to invoke handler directly
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
enhancement
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@ikitommi