Gaia/Architecture Proposal: Difference between revisions

Line 332: Line 332:
= Memory Management =
= Memory Management =


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.
While one of the goal of this architecture is to free the main thread (using it for 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 is a bottleneck.


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.
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 as much memory as we can.


Then, when the app is coming back to foreground, those can be restored to maximize the user-experience.
Then, when the app is coming back to foreground, those non user-facing parts can be restored to maximize the user-experience.


[[File:Gaia Architecture Proposal App Architecture Background WithWebAPIs.png|400px]]
[[File:Gaia Architecture Proposal App Architecture Background WithWebAPIs.png|400px]]
Confirmed users
230

edits