Changes in 806311b: Updated Izenda Caching Lifecycle (markdown)

				FAQ/Izenda-Caching-Lifecycle.md
			
          @@ -140,4 +140,6 @@ When the data is requested from the given cache by the successive block through 

           If cache doesn't find data - then it requests this data through the arrow "incoming" into its figure from the previous block. When previous block produces this data, cache stores it and also sends it to the successive block through "outgoing" arrow.

          -So there is no any kind of "full cycle of data flow" through all these arrows each time when user does something. Instead, each of these caches work like buffer/accumulator/floodgate - each of them acts independently in the data flow into which it is inserted, either returning previously cached data with prevention of "deeper" blocks work. Or if data is not cached yet - then it passes execution to the "deeper" blocks of code which should produce necessary data.

          \ No newline at end of file

          +So there is no any kind of "full cycle of data flow" through all these arrows each time when user does something. Instead, each of these caches work like buffer/accumulator/floodgate - each of them acts independently in the data flow into which it is inserted, either returning previously cached data with prevention of "deeper" blocks work. Or if data is not cached yet - then it passes execution to the "deeper" blocks of code which should produce necessary data.

          +

          +![Caching Lifecycle](/FAQ/Izenda-Caching-Lifecycle/Caching-Lifecycle.png)

          \ No newline at end of file

...	...	@@ -140,4 +140,6 @@ When the data is requested from the given cache by the successive block through
140	140
141	141	If cache doesn't find data - then it requests this data through the arrow "incoming" into its figure from the previous block. When previous block produces this data, cache stores it and also sends it to the successive block through "outgoing" arrow.
142	142
143		-So there is no any kind of "full cycle of data flow" through all these arrows each time when user does something. Instead, each of these caches work like buffer/accumulator/floodgate - each of them acts independently in the data flow into which it is inserted, either returning previously cached data with prevention of "deeper" blocks work. Or if data is not cached yet - then it passes execution to the "deeper" blocks of code which should produce necessary data.
...	...	\ No newline at end of file
	0	+So there is no any kind of "full cycle of data flow" through all these arrows each time when user does something. Instead, each of these caches work like buffer/accumulator/floodgate - each of them acts independently in the data flow into which it is inserted, either returning previously cached data with prevention of "deeper" blocks work. Or if data is not cached yet - then it passes execution to the "deeper" blocks of code which should produce necessary data.
	1	+
	2	+![Caching Lifecycle](/FAQ/Izenda-Caching-Lifecycle/Caching-Lifecycle.png)
...	...	\ No newline at end of file