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.

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

Clients correlated with Service definitions for server/client streaming services #30

Closed
3 tasks
juanpedromoreno opened this issue Jul 10, 2017 · 1 comment
Assignees
Milestone

Comments

@juanpedromoreno
Copy link
Member

We should cover services with these variants:

  • Clients correlated with Service definitions for client streaming services
  • Clients correlated with Service definitions for server streaming services
  • Clients correlated with Service definitions for bidirectional streaming services

Part of this job will be to figure out which pattern fits better for observer/observable patterns.

@juanpedromoreno juanpedromoreno added this to the Sprint 1 milestone Jul 10, 2017
@juanpedromoreno juanpedromoreno self-assigned this Jul 10, 2017
@anamariamv anamariamv modified the milestones: Sprint 2, Sprint 1 Jul 12, 2017
@juanpedromoreno
Copy link
Member Author

juanpedromoreno commented Jul 18, 2017

After some investigation, we can provide Observable as the data type by default to manage the streaming APIs, avoiding the use of the Java StreamObserver type.

As you can see in the Design Summary section, in terms of frees algebras, assuming that R is the output type for each service:

  • unary services and client-to-server streaming services: they can simply return FS[R].
  • server-to-client and bi-directional services: they would return FS[monix.reactive.Observable[R]].

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants