Deprecate activity/fragment binding.

[JakeWharton]

Closes #95.

[dlew]

👍

[mttkay]

I don't think we can remove this until we introduce a variant of
HandlerThreadScheduler that executes synchronously when already on the main
thread. There were multiple long wound discussions around this. The problem
is that OperatorObserveOn posts unsubscribe on the main looper, even when
it's already on the main thread. This means that between unsubscribing and
Android destroying the views a window of time opens where the subscriber
gets a notification but the fragment is detached.

I don't see how the new life cycle observable fixes that.

We shouldn't deprecate this unless there's a better alternative available.
On Nov 29, 2014 2:07 PM, "Daniel Lew" [email protected] wrote:

[image: 👍]

—
Reply to this email directly or view it on GitHub
#105 (comment).

[dpsm]

@mttkay I thought we did auto unsubscribe when the lifecycle "closes" didn't we? I am not sure if we ever fixed this ReactiveX/RxJava#1292

[dlew]

@mttkay Interesting. I'll have to think on it.

[JakeWharton]

Cool. Closing to ensure discussion happens on the issue.

[dlew]

@mttkay Do you have links to any of the previous discussions, so we don't rehash it? I'd like to read through them then try to figure out a way around.