On 10/12/05, Hubert Rabago <[EMAIL PROTECTED]> wrote: > I'm still trying to understand why the distinction is important. :) > > Someone help me!
Right now, a lot of Java web applications flit from action to action. We migth use one action to display the page the first time, and then submit to another action after the form is filled out, and so forth. But, another popular paradigm, going back to the Perl days, is to keep submitting back to the same URI. The first time the page is retrieved, it is by GET. After that, it is submitted back by POST (aka PostBack). In an environment like JSF or ASP.NET, the framework makes a clear distinction between the initial GET and subsequent POSTs. During the GET, we prepopulate the components, which then retain their state across the subsequent POSTs. Eventually, when the Use Case for the page is resolved, we would transfer to another page. But most JSF or ASP.NET wizards just keep POSTing back to the same page until the task is complete. Apparently, Michael wants to do something simliar with Struts Dialogs, which seems reasonable to me, if there's a reasonable way to do it. -Ted. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
