According to the documentation ( http://reactivex.io/documentation/operators/flatmap.html ) the switchMap is like the flatMap, but it will only emit items from the new observable until a new event is emitted from the source observable. The marble diagram shows it well. Notice the difference in the diagrams: In switchMap the second original emission (green marble) does not … Read more
map transform one event to another. flatMap transform one event to zero or more event. (this is taken from IntroToRx) As you want to transform your json to an object, using map should be enough. Dealing with the FileNotFoundException is another problem (using map or flatmap wouldn’t solve this issue). To solve your Exception problem, … Read more
Great questions, I think the documentation could do with some more detail. io() is backed by an unbounded thread-pool and is the sort of thing you’d use for non-computationally intensive tasks, that is stuff that doesn’t put much load on the CPU. So yep interaction with the file system, interaction with databases or services on … Read more
Futures Futures were introduced in Java 5 (2004). They’re basically placeholders for a result of an operation that hasn’t finished yet. Once the operation finishes, the Future will contain that result. For example, an operation can be a Runnable or Callable instance that is submitted to an ExecutorService. The submitter of the operation can use … Read more
For simple networking stuff, the advantages of RxJava over Callback is very limited. The simple getUserPhoto example: RxJava: api.getUserPhoto(photoId) .observeOn(AndroidSchedulers.mainThread()) .subscribe(new Action1<Photo>() { @Override public void call(Photo photo) { // do some stuff with your photo } }); Callback: api.getUserPhoto(photoId, new Callback<Photo>() { @Override public void onSuccess(Photo photo, Response response) { } }); The RxJava … Read more