Component Architecture
Why?
-
Reusable modules
-
Performance optimization
- Support newer MVC components in Web
Server-side components
-
Lives in Components area
-
Requested from view (strongly typed methods)
-
Uses Accept-Type to decide what to return
- Splits response into chunks, sends to the right spot
When to use
-
Reusable piece of functionality/behavior
-
Content chunk with several different views
- Shared between Web and MVC
LazyHorse
Asynchronous static content Hoarder and Loader
Features
-
Load HTML, CSS, JScontent on demand
-
Uses promise pattern for callback hooks
-
Does not let duplicate content to be downloaded
-
Multiple instances of LazyHorse can co-exist
- Can download resources in parallel of in the order specified by user
When to use
-
Control/widget with behavior
-
Don’t want it to block page loading
- Might not even be used
Demos
Component Architecture
By Daniel Poindexter
