----- Original Message ----- From: "Kruse, Matt" <[EMAIL PROTECTED]> To: "Struts Users Mailing List" <[EMAIL PROTECTED]> Sent: Thursday, September 18, 2003 3:42 PM Subject: RE: Is it possible to remove *.do or /do/* from the URL
> > The important principle here is "Web Application != Web > > Site". > > Why? In many cases, it's the same difference. These days, web "sites" > usually are web "applications" on the back-end. There are a lot of stupid > users out there. In many cases, every attempt needs to be made to cater to > them. > What Craig could possibly mean is that a Web Application contains most of non-idempotent actions while a Web Site contains only idempotent actions. Partitioning user actions to web servers into idempotent and non-idempotent actions is going to be our foundation theory that combines Model-1 resources and Model-2 applications into one environment as follows: Model-1 resources are grouped under idempotent modules, in which no-cache is set to false; Model-2 applications are groups under non-idempotent modules, in which no-cache is set to true and form token checking is automatically performed. Under this structure, end users could use bookmark and the browser's Back button when they navigate in idempotent modules. However, when they navigate in non-idempotent modules, they will get "Page has Expired" if they use the Back button. One problem in the theory is that when they get this message, the application flow is interrupted. The problem could be resolved in our future algorithms. > > If your users feel compelled to use bookmarks and the back button in > > your webapps, despite efforts to train them correctly, this is a pretty > > good sign that you have not provided enough suitable navigation > > controls in your basic UI. > > On the contrary, I'd say that if your web application can't handle the back > button and bookmarking, then you've designed it incorrectly. ESPECIALLY if > your users want to use them :) > We would group them (marketing stuff, bookmarks, etc.) into idempotent modules. > When web "applications" are done right, they have nice URL's, the back > button can be used without causing any problems, and bookmarking is possible > wherever it makes sense. > > IMO, there are too many lazy developers out there who do poor design and > don't consider the 'Back' button, for example, then look for cheap hacks to > stop the user from using it. Instead, they should think differently and > handle these cases. It's sometimes more work, sure, but that's part of the > job! If we find a page has a non-idempotent action, the page should be put into non-idempotent modules, in which the Refresh/Back/Forward buttons will not generate repeated actions, even end users type keyboard commands, right-click and select these commands... > > Matt > > Jing Netspread Carrier http://www.netspread.com --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
