A
Abdullah Kauchali
Hi folks,
(Need comments if you have done something like this before. Any response
would be greatly appreciated.)
We've recently been prototyping the idea of completely avoiding the server
building the eventual/final HTML for the browsers. So far we've got this:
1. Create separate ASP pages that talk to the COM business components (say:
businessproc.asp);
2. These ASP pages do a predefined number of non-visual business "actions"
(e.g your CRUDs);
3. The businessproc.asp page is embedded (?) into a user-interface HTML
page (ui.htm) as an hidden iframe;
4. The business actions of the hidden iframe'd businessproc.asp are
triggered via JavaScript (there is a "runner" javascript function on the
businessproc.asp page that acts as a receiving point which also does a form
post triggering the correct "action");
5. The results of the businessproc.asp are then PUSHED into the parent
UI.HTM page once the business action is complete (once businessproc.asp
returns);
6. The receiving functions of this post-back on the UI.HTM page then
"paint" the appropriate controls. (Cycle complete)
Has anyone done this before? (Any links etc) What are the general caveats
of this approach?
Many thanks in advance,
Regards
Abdullah
(Need comments if you have done something like this before. Any response
would be greatly appreciated.)
We've recently been prototyping the idea of completely avoiding the server
building the eventual/final HTML for the browsers. So far we've got this:
1. Create separate ASP pages that talk to the COM business components (say:
businessproc.asp);
2. These ASP pages do a predefined number of non-visual business "actions"
(e.g your CRUDs);
3. The businessproc.asp page is embedded (?) into a user-interface HTML
page (ui.htm) as an hidden iframe;
4. The business actions of the hidden iframe'd businessproc.asp are
triggered via JavaScript (there is a "runner" javascript function on the
businessproc.asp page that acts as a receiving point which also does a form
post triggering the correct "action");
5. The results of the businessproc.asp are then PUSHED into the parent
UI.HTM page once the business action is complete (once businessproc.asp
returns);
6. The receiving functions of this post-back on the UI.HTM page then
"paint" the appropriate controls. (Cycle complete)
Has anyone done this before? (Any links etc) What are the general caveats
of this approach?
Many thanks in advance,
Regards
Abdullah