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

Support rx.Single from RxJava? #969

Closed
plastiv opened this Issue Jul 21, 2015 · 2 comments

Comments

3 participants
@plastiv

plastiv commented Jul 21, 2015

With rx.Single released as experimented type of Observable do you see the value in supporting it as a return type for network requests?
https://github.com/ReactiveX/RxJava/blob/1.x/CHANGES.md#rxsingle
ReactiveX/RxJava#1594 (comment)

Quote from there:

A Single will always behave in one of 3 ways:

1) respond with an error
2) never respond
3) respond with a success

An Observable on the other hand may:

1) response with an error
2) never respond
3) respond successfully with no data and terminate
4) respond successfully with a single value and terminate
5) respond successfully with multiple values and terminate
7) respond successfully with one or more values and never terminate (waiting for more data)
@JakeWharton

This comment has been minimized.

Show comment
Hide comment
@JakeWharton

JakeWharton Jul 21, 2015

Collaborator

We are aware and it may be added. It's experimental nature adds a level of
volatility that if we choose to add it as the API may change in a
backwards-incompatible way.

On Tue, Jul 21, 2015, 3:12 AM Sergii Pechenizkyi notifications@github.com
wrote:

With rx.Single released as experimented type of Observable do you see the
value in supporting it as a return type for network requests?
https://github.com/ReactiveX/RxJava/blob/1.x/CHANGES.md#rxsingle
ReactiveX/RxJava#1594 (comment)
ReactiveX/RxJava#1594 (comment)

Quote from there:

A Single will always behave in one of 3 ways:

  1. respond with an error
  2. never respond
  3. respond with a success

An Observable on the other hand may:

  1. response with an error
  2. never respond
  3. respond successfully with no data and terminate
  4. respond successfully with a single value and terminate
  5. respond successfully with multiple values and terminate
  6. respond successfully with one or more values and never terminate (waiting for more data)


Reply to this email directly or view it on GitHub
#969.

Collaborator

JakeWharton commented Jul 21, 2015

We are aware and it may be added. It's experimental nature adds a level of
volatility that if we choose to add it as the API may change in a
backwards-incompatible way.

On Tue, Jul 21, 2015, 3:12 AM Sergii Pechenizkyi notifications@github.com
wrote:

With rx.Single released as experimented type of Observable do you see the
value in supporting it as a return type for network requests?
https://github.com/ReactiveX/RxJava/blob/1.x/CHANGES.md#rxsingle
ReactiveX/RxJava#1594 (comment)
ReactiveX/RxJava#1594 (comment)

Quote from there:

A Single will always behave in one of 3 ways:

  1. respond with an error
  2. never respond
  3. respond with a success

An Observable on the other hand may:

  1. response with an error
  2. never respond
  3. respond successfully with no data and terminate
  4. respond successfully with a single value and terminate
  5. respond successfully with multiple values and terminate
  6. respond successfully with one or more values and never terminate (waiting for more data)


Reply to this email directly or view it on GitHub
#969.

@svenjacobs

This comment has been minimized.

Show comment
Hide comment
@svenjacobs

svenjacobs Jul 22, 2015

+1 for Single :)

svenjacobs commented Jul 22, 2015

+1 for Single :)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment