Skip to content

Change Java future observable implementation from blocking to non blocking #1460

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

Closed
wants to merge 3 commits into from

Conversation

tbak
Copy link

@tbak tbak commented Jul 17, 2014

No description provided.

@cloudbees-pull-request-builder

RxJava-pull-requests #1412 FAILURE
Looks like there's a problem with this pull request

@cloudbees-pull-request-builder

RxJava-pull-requests #1413 SUCCESS
This pull request looks good

@akarnokd
Copy link
Member

Generally, we don't do polling but rather use Schedulers.io() for blocking threads; I'm not certain if we want to change into this direction.

@benjchristensen
Copy link
Member

This is being pursued due to the high cost of having a 1:1 relationship of thread to Future.

@@ -61,34 +79,69 @@ public void call() {
that.cancel(true);
}
}));
new FuturePollingTask(subscriber).call();
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This contains a Scheduler.Worker instance that never gets cleaned up. It also needs to be registered for unsubscribe via subscriber.add.

@benjchristensen benjchristensen added this to the 0.20 milestone Jul 21, 2014
@cloudbees-pull-request-builder

RxJava-pull-requests #1424 SUCCESS
This pull request looks good

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

Successfully merging this pull request may close these issues.

4 participants