Page Comparison

...

Not a big deal? Programmers have been doing that for centuries? This might be so, but compare this to a web form that spawns another web form. ASP.NET provides no mechanism for all that:

• state must be passed between windows in the ViewState or worse
• no typing, all ViewState values are object|s
• no maintenance of a stack – the callee must deliberately jump back into the caller (GOTO!)
• between "calling" and "returning", there is a post-back each, and no natural flow of execution

re-call solves all these problems and gives you the illusion of

• passing of typed values between web forms
• continuous operation/flow of execution across post-backs
• transparent maintenance of a "stack" of windows/arguments
• natural exception handling – an exception thrown by a callee can be
  caught by any caller up (or better: down) the "stack"

Note that, in the world of regular procedural desktop applications, a function is associated with each window. re-call gives you the same orderly manner of conducting business; for this reason, the term "re-call function" is synonymous with "re-call page". An old name for re-call is "WXE", for "web execution engine", so don't be confused if you find "WXE function", "re-call functions", "WXE page" and "WXE function" in forum traffic or documentation. They all mean the same thing, namely, something like this:

...