rx-java

问题 I have two Observable s, let's call them PeanutButter and Jelly . I'd like to combine them to a Sandwich Observable . I can do that using: Observable<PeanutButter> peanutButterObservable = ...; Observable<Jelly> jellyObservable = ...; Observable<Sandwich> sandwichObservable = Observable.combineLatest( peanutButterObservable, jellyObservable, (pb, j) -> makeSandwich(pb, j)) The problem is that RX waits for the first PeanutButter and the first Jelly to be emitted before emitting the first

问题 I have two Observable s, let's call them PeanutButter and Jelly . I'd like to combine them to a Sandwich Observable . I can do that using: Observable<PeanutButter> peanutButterObservable = ...; Observable<Jelly> jellyObservable = ...; Observable<Sandwich> sandwichObservable = Observable.combineLatest( peanutButterObservable, jellyObservable, (pb, j) -> makeSandwich(pb, j)) The problem is that RX waits for the first PeanutButter and the first Jelly to be emitted before emitting the first

问题 What is the benefit of using Retrofit in combination with Rxjava? 回答1: Question Retrofit Already in run on background thread. Then why need another background task RxJava? I think most importanly, avoid nested callbacks( callback hell ). e.g) Callback hell (Retrofit) public interface MyService { @GET("users") Call<List<UserModel>> getUser(); @GET("userinfo") Call<UserInfoModel> getUserInfoById(@Query("id") Integer id); } service.getUser().enqueue(new Callback<UserModel>() { @Override public

问题 I have this code which I can use with concat but what I need is a way of passing Iterator so that I can add or remove items which isn't possible with this code. I want to be able to remove and add items to concat without causing java.util.ConcurrentModificationException I need to do this for different purpose such as if some items are success remove them and retry others. Or if token is invalid then remove all and refresh token and add all with modified token. Observable userObservable =

问题 I have a singleton that takes a few seconds to instantiate. It makes the UI freezes. So I'm planning to make the getInstance() method asynchronous. Is writing the following code a common practice? /* * The singleton class */ public class Singleton { private static volatile Singleton instance; public static Observable<Singleton> getInstance(Context context) { return Observable.fromCallable(() -> { synchronized (Singleton.class) { if (instance == null) instance = new Singleton(context

问题 I have a collection of 20 items, I will create a loop for the items and make API Calls to get the data, based on the data returned, I will have to update in the database. This requirement is simple and I am able to accomplish in plain Java. Now for performance, I am learning about using RxJava . I went through many articles in the internet and found that people refer to the async-http-client library for async http calls, I find that the library is out of date and the maintainer is planning

问题 I have a collection of 20 items, I will create a loop for the items and make API Calls to get the data, based on the data returned, I will have to update in the database. This requirement is simple and I am able to accomplish in plain Java. Now for performance, I am learning about using RxJava . I went through many articles in the internet and found that people refer to the async-http-client library for async http calls, I find that the library is out of date and the maintainer is planning

问题 The following code emits items from observable1 only after observable2 is completed. observable1.startWith(observable2) .subscribe() I need to achieve another behavior observable1 -> 0 1 2 3 observable2 -> 1 2 3 4 5 6 observable1.startWithDefault(observable2) -> 1 2 0 1 2 3 The second observable emits items only while first observable is empty and then items from first one are emited. I could not find correct solution using only basic operators, what is correct RxJava 2 implementation of

问题 I have and Android app with the view class ( Fragment , Activity ) observing its ViewModel . The ViewModel exposes methods such as getUserName which returns Observable<String> . Although maybe there is a possibility to find a better name (maybe observeUserName ), I'm happy with the current one - it is quite explanatory. However, here starts the hard part: ViewModel also can tell the view to perform some operation - for example close itself, pop backstack etc. For this case ViewModel defines

问题 This is the case: I have the domain layer to provide data fetching interface for business logics, and I have 2 data sources: local database and remote network. It works like this: Request all users: DataRepository.getInstance().getUsers(); In DataRepository, there are 2 sources: LocalDataSource.getUsers() which fetches all users from local database, if there is no data then ignore this request. RemoteDataSource.getUsers() which requests latest user list from our server(Even if there is data