On Fri, 2010-01-29 at 08:47 -0500, Mossman, Paul AVAYA (CAR:9D30) wrote: > > What's wrong with using the refresh button on the browser? > > Depending on how you got to the page, you can sometimes get that browser > message about re-sending information that will repeat any action.
There is a simple way to prevent that, and we should be using it more. That happens when you get to the page by using a POST request - if the POST request does whatever it's going to do and then returns a redirection (302) http response, the browser will then do a GET to whatever URL the server redirected to, and that page will not have the repeated action warning on subsequent refreshes. I don't know whether implementing that paradigm is easy in our framework or not, but doing it makes for a _much_ better web application experience. > Having a Refresh button makes sense to me. I don't object to that in principle, but I wouldn't make adding Refresh buttons a very high priority... _______________________________________________ sipx-dev mailing list [email protected] List Archive: http://list.sipfoundry.org/archive/sipx-dev Unsubscribe: http://list.sipfoundry.org/mailman/listinfo/sipx-dev sipXecs IP PBX -- http://www.sipfoundry.org/
