On 7/7/05, Rick Reumann <[EMAIL PROTECTED]> wrote: > klute wrote the following on 7/7/2005 3:07 PM: > > > It seems like it would make sense to have both so that > > you can use GET to set up a particular form and POST > > to process that form. Instead, I'd have to look at the > > request to see what was invoked and then conditionally > > do some processing. > > No need for conditional process based on GET or POST, you should be > either directing control based on either... > > A) Separate mappings that point to different Action classes > > /setUpEdit.do > /edit.do > > or > > B) pass in a dispatch parameter if using a DispatchAction (You can still > use separate mappings also if you want also). > > -- > Rick
Not quite. POST is generally for data input (form processing). GET is generally for pulling static pages or semi-static result pages or at least for performing idemponent actions. These methods have different semantics. This difference is the cornerstone of approach that I use now [plug skipped]. Michael. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
