Split "Online" and "Offline" AudioContext processing

Source/platform/audio/Reverb.h

Index: Source/platform/audio/Reverb.h
diff --git a/Source/platform/audio/Reverb.h b/Source/platform/audio/Reverb.h
index 191b2576a1eb5ab3f000bfe8dae71f77d2ad12c4..4a5d670a8ebe001b0fbb7793b5e619ac8282e1fd 100644
--- a/Source/platform/audio/Reverb.h
+++ b/Source/platform/audio/Reverb.h
@@ -45,7 +45,7 @@ public:
     enum { MaxFrameSize = 256 };
 
     // renderSliceSize is a rendering hint, so the FFTs can be optimized to not all occur at the same time (very bad when rendering on a real-time thread).
-    Reverb(AudioBus* impulseResponseBuffer, size_t renderSliceSize, size_t maxFFTSize, size_t numberOfChannels, bool useBackgroundThreads, bool normalize);
+    Reverb(AudioBus* impulseResponseBuffer, size_t renderSliceSize, size_t maxFFTSize, size_t numberOfChannels, bool hasRealtimeConstraint, bool normalize);

[Raymond Toy, 2015/06/27 15:38:11]

DBC:  I think useBackgroundThreads is clearer than hasRealtimeConstraints. 
While we don't allow it today, it seems possible that we might want multiple
threads for the reverb, even for offline contexts.

Same comment for ReverbConvolver.h

 
     void process(const AudioBus* sourceBus, AudioBus* destinationBus, size_t framesToProcess);
     void reset();