anchor.diff:  
   b) _"While Rx has concurrency features, these should not be mistaken for a concurrency framework. Rx is designed for querying data, and as discussed in the first chapter, parallel computations or composition of asynchronous methods is more appropriate for other frameworks."_
   
  -I would sum this up to:
  +==== My summary concerning threading and parallelsim with RxJava (1.0.14)
   
   Rx is created mainly for "clients" (client applications like apps, desktop gui applications, ...) where
  -you have typically one thread from the GUI and you would like to "spin off" several background tasks (in parallel) when an event like submitting a form happens,
  -combine these asynchronously returning background task-results to one result which you display in the GUI. It's not primarly made for "servers",
  -e.g. to handle concurrent HTTP requests in a webserver. But you can use it to do implement "servers", if you know "how".
  +you have typically one thread from the GUI and you would like to "spin off" several background tasks (in parallel).
   
  -See also https://github.com/ReactiveX/RxJava/issues/1673 and the section about schedulers in http://www.pluralsight.com/courses/reactive-programming-java-8-rxjava.
  +Rx is excellent at that, at doing _different_ things in parallel.
  +
  +When it comes to doing _same_ things in parallel, like in a server where you handle hundreds of client calls in parallel,
  +then Rx is not that straight forward. You start with creating Observables, using subscribeOn and flatMap, just to get
  +_same_ things to run in parallel. Here are some examples for this.
  +
   
   === OneLaneMcDrive
   
  
positive.code: == Threading and Parallelism with RxJava and Java 8
  
  Probably you also had a difficult start concerning RxJava and threading like http://www.grahamlea.com/2014/07/rxjava-threading-examples[Graham Lea did].
  
  
negative.code: Same as OneLaneMcDrive, but now with more customers arriving. The McDrive can't handle all of them "just in time",
  so a wait line (queue) builds up. The longer the example runs, the longer the wait line becomes.
  
  We need some kind of backpressure: we choose buffering (queueing) and get a "jam" (queue becomes longer and longer).
  
  === InfiniteLaneMcDrive
  
  