I've dug into the demos and they are informative, to a point. However, I'm looking for something that describes the component lifecycle for a non-trivial application. I'll trace out a scenario with some questions.
Let's say I'm using Java servlets. My _initial_ UI is specified declaratively in index.xap, so I presume that my index.html/jsp will follow the "bootstrap shell" seen in the demos. The initial app is served from "/apps/Test/index.xap". According to RequestService, any requests must be relative to the app context (e.g. index.xap) so any subsequent calls would be to URLs such as /apps/Test/srv/foo or /apps/Test/srv/bar.jsp. After the initial UI appears, the user can enter some input, click a button and a table will refresh with their search results.... Q: I presume that all client-side service consumers use RequestService via the session, yes? Q: Is it preferable for all consumers of server services to use one parameterized "service URL" or separate function-specific URLs? Or does this boil down to taste/style/maintainability? Q: If in addition to the data update I also want to download some additional UI code, I can see how XModify could handle the UI spec. But then the server would need to maintain some state so that this UI spec is not downloaded again, yes? Also, by what means does any js/"handler code" required by the new UI elements get downloaded? If these sorts of questions are addressed by a document or sample application, a pointer would be greatly appreciated! Thank you, David
