Gaia/Architecture Proposal: Difference between revisions

Gaia/Architecture Proposal (view source)

4 bytes removed , 6 March 2015

m

Confirmed users

51

edits

@@ Line 333: / Line 333: @@
 = Memory Management =
-While one of the goal of this architecture is to free the UI thread and reserve it for UI related tasks only, and sharing the related logic for instant bookmarks, actions, activities, there may be times where the memory limitation of the device are the bottleneck.
+While one of the goal of this architecture is to free the main thread (using it UI related tasks only), and to share the related logic for instant bookmarks, actions, activities, there may be times where the memory limitations of the device are the bottleneck.
-For such devices, the model offers a macro memory management. So when the application goes in background, most of the user non-visible parts can be shutdown (in red here) in order to safely recover memory.
+For such devices, the model offers a macro memory management. So when the application goes in background, most of the non user-facing parts (in red here) can be shutdown safely in order to recover memory.
-Then when the app is going to foreground again, those can be restored to maximize the user-experience.
+Then, when the app is coming back to foreground, those can be restored to maximize the user-experience.
 [[File:Gaia Architecture Proposal App Architecture Background WithWebAPIs.png|400px]]