An exploration of application structure patterns, from purely server oriented request/response flow to fully featured client applications in the browser
you’re just coding single page • not a client app • manipulation mostly presentational • few data communications • user interaction brief, simple, infrequent
richness” • occassional data communications • multiple parts of a page need to reflect data • shallow view hierarchy (1-2 levels) • small number of views (~7) • user interaction brief and/or infrequent
need to reflect data • deep view hierarchy (2-3+) • large number of views • user will remain for large amounts of time • and/or frequently return • server is just an api • you’d *almost* write a desktop/iOS app