Changes between Version 3 and Version 4 of DeveloperGuidelines/EdenMobile/Concepts


Ignore:
Timestamp:
03/30/17 11:02:43 (7 years ago)
Author:
Dominic König
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • DeveloperGuidelines/EdenMobile/Concepts

    v3 v4  
    1616The most confusing part for developers coming from the Sahana Eden web application may be the inescapable asynchronism in EdenMobile.
    1717
    18 Events can occur at any time, independently of each other - so many state changes can happen in parallel. Introspecting state and carefully maintaining scope are thus key requirements for any EdenMobile functionality.
     18Events can occur at any time and independently of each other - so many state changes can happen in parallel. Introspecting state and carefully maintaining scope are thus key requirements for any EdenMobile functionality.
    1919
    20 At the same time, all access to back-end resources is asynchronous as well - so the return of control to the caller (=the user, eventually) always comes first, before the response, and flow control, in the vast majority of cases, requires management of deferred objects and callback chains.
     20At the same time, all access to back-end resources is asynchronous as well - so the return of control to the caller (=the user, eventually) always comes first (i.e. before the response), and flow control, in the vast majority of cases, requires management of deferred objects and callback chains.
    2121
    2222=== No Models? ===