Why Not RxLifecycle?
Hello. This is Dan Lew. You may or may not know me as the author of RxLifecycle. Here’s why I’ve started pulling back from using my creation. Origins When Trello first started using RxJava, we were dismayed with how easy it was to leak memory when using it. Seemingly any Subscription you setup would leak unless you explicitly cleared it. As such, we were constantly juggling Subscriptions and unsub
Model View Whatever + Rx のアンチパターン - Re.Ra.Ku tech blog
GUIアーキテクチャパターンとしてModel View Whateverを採用した際に、Rxのストリームをプレゼンテーション層からモデル層まで一気通貫でつなげてしまうのはアンチパターンである、という話をします。 前提 GUIアーキテクチャパターンにおける Model View Whatever パターン、とくにMVVMに近いパターンを前提とします。いわゆるサーバサイドの「web系MVC」は前提としません。 Model View WhateverパターンとPDS そもそもGUIアプリケーションでModel View Whateverというアーキテクチャパターンを採用する理由として、PDSの実現があります。このあたりの話は詳しくは実況中継シリーズ Vue.jsで実現するMVVMパターン Fluxアーキテクチャとの距離 - Re.Ra.Ku アドベントカレンダー day 13 - Re.Ra.K
How to leak memory with Subscriptions in RxJava
Look out!This article is outdated as it covers and old version of RxJava— you can find the updated version for RxJava2 here: https://medium.com/@scanarch/how-to-leak-memory-with-disposables-in-rxjava2-715dd80bf966 — — — — — — — — There are plenty of great how-to articles about RxJava. It does simplify things significantly when working with Android framework but be careful because simplification ma
RxJava meets Android Data Binding
Probably every Android developer is using or at least heard about RxJava. Currently, there are lots of libraries that use the reactive approach, let RxPreferences, RxLocation, RxPermissions, RxWear, RxBinding serve as an example. But let’s go back to the beginning. Here at Tango we are using RxJava in every Android project because it accelerates application development and helps us in the fight wi
RxJava's repeatWhen and retryWhen, explained
repeatWhen and retryWhen are fairly baffling at first glance. For starters, they are serious contenders for "most confusing marble diagrams": They're useful operators: they allow you to conditionally resubscribe to Observables that have terminated. I recently studied how they worked and I want to try to explain them (since it took me a while to grasp). Repeat vs. Retry First of all, what is the di
Loading data from multiple sources with RxJava
Suppose I have some Data that I query from the network. I could simply hit the network each time I need the data, but caching the data on disk and in memory would be much more efficient. More specifically, I want a setup that: Occasionally performs queries from the network for fresh data. Retrieves data as quickly as possible otherwise (by caching network results). I'd like to present an implement
Unit Testing RxJava Observables
The first step to rx-ify our architecture was to change the methods in the data layer so that they returned Observables. The next question was: how do we unit test this? The ugly wayThe first thing that came to our minds was to simply subscribe in the same way we would from outside the tests and then save the result in a global variable that can later on be asserted. For example, imagine we have a
Don't break the chain: use RxJava's compose() operator
One nice aspect of RxJava is that you can see how data is transformed through a series of operators: Observable.from(someSource) .map(data -> manipulate(data)) .subscribeOn(Schedulers.io()) .observeOn(AndroidSchedulers.mainThread()) .subscribe(data -> doSomething(data)); What if you have a set of operators that you want to reuse for multiple streams? For example, I frequently use subscribeOn() and
RxJava, Tips and Tricks
public interface Observer <T> { void onCompleted(); void onError(java.lang.Throwable throwable); void onNext(T t); } public class Observable <T> { public final static <T> Observable<T> create(OnSubscribe<T> f) public rx.Subscription subscribe(rx.Observer<? super T> observer) // ... } public static interface OnSubscribe<T> extends Action1<Subscriber<? super T>> {} public interface Subscription { pu
Release 1.0.0 · ReactiveX/RxJava
After 2+ years of internal and open source development, 3600+ commits, 100+ releases, and with the help of 97 contributors RxJava has hit version 1.0.0. Thank you @headinthebox @zsxwing @samuelgruetter @akarnokd @quidryan @DavidMGross @abersnaze @jmhofer @mairbek @mttkay @daveray @mattrjacobs @michaeldejong @MarioAriasC @johngmyers @pron @jbripley @davidmoten @gliptak @johnhmarks @jloisel @billyy
Using RxJava with Android
If you’re into Android (and Java) development, there is a good chance you’ve already heard about RxJava, which is a Java implementation of Reactive Extensions developed by Netflix. Reactive Extensions is a library to compose asynchronous and event-based programs using observable collections and LINQ-style query operators, quoted from the corresponding MSDN site. Netflix made the library available
リリース、障害情報などのサービスのお知らせ
最新の人気エントリーの配信
j次のブックマーク
k前のブックマーク
lあとで読む
eコメント一覧を開く
oページを開く
ログイン - はてな
onError throws Exception after Flowable has been unsubscribed · Issue #4894 · ReactiveX/RxJava
`Rxify` — a simple spell for complex RxJava operators (Part -3)
RxJava学習のベストプラクティスっぽいもの
Native Vs. Hybrid App Development: 5 Reasons To Go Native - stable|kernel
Recursive Observables with RxJava
The History of Reactive Extensions
分かった気になるはじめてのRxJava
Retrofit and RxJava (Netflix Open Source Meetup S02E02 07/2014) // Speaker Deck
