How it works, end to end
Two strings per request, one handler, a new instance every time — and the one click, one request model every app is written against.
12 essays · start with #5
- #5UI5 Over-the-Wireevery request answered with two strings
- #16One Click, One RequestPBO, PAI, and the dispatch in main( )
- #6The Frontend Knows Nothingone shell for every app, and why it never needs a redeploy
- #7One Handler for Every Appno service per screen, and what the handler leaves to the apps
- #8Only the Changed Partthe view stays, the model updates
- #9A New Instance on Every Requestserialized state, and what that asks of the class
- #10Swapping the View at Runtimea different control, chosen in an IF
- #11No Build, No Deploy, No Cachechange, activate, refresh — and where a BSP still enters
- #12Where Your Own JavaScript Goesthree declared seams, no plugin system
- #13Four Verbs, Every Controlwhy the view builder knows no controls
- #14A Classrun for the Browserthe shape it copied
- #15Where the Selection Screen Wentthe variable and the field are one declaration again