This is an anti-pattern. You should make sure that all screens that can be navigated to by the user are stateless in the sense that all the state can be derived from the URL. The big advantage is that the screen can be bookmarked users can navigate to it directly. If you are concerned about redundant backend calls encapsulate the backend calls in a seperate (singleton class) that handles caching. This will also reducate the logic in your Presenters because you don't have to check the URL parameters against the already fetched data.
On Wednesday, March 11, 2015 at 8:26:01 AM UTC+1, Abdullah wrote: > > Hi, > Is any Impact Implementing MVP Pattern Without History Mechanism? > -- You received this message because you are subscribed to the Google Groups "Google Web Toolkit" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/google-web-toolkit. For more options, visit https://groups.google.com/d/optout.
