A GWT application is a web application. So that's easy :-) Any time you open a new tab in a browser, or a tab in another browser, you get a new copy of the application. This new copy has no connection with any other copy that is running (unless you design it, say, to use cookies for some reason to hold state for the next time the user goes to your site). Nothing you do in one window will affect what happens in another tab or browser.
The server just provides services ad hoc to anything that asks for them, you don't keep state on the server so you don't need sessions, for example. The server doesn't know or care where the requests for services come from, it just supplies the data. If you had a shopping cart, you can keep all the selected items on the client. If the user wants to delete an item, you do it on the client and don't bother the server. If the user wants to look at the details of another product, you get the information from the server. If they decide to buy, you don't go back to the server, you just add it to the list kept in the client. If the user has two copies of the site open, adding an item in one tab doesn't affect the contents of the cart in the other tab. If the user closes one tab, everything in that cart is lost. Everything in the other cart is still there. You can alter this behaviour but you would have to actively code for it. Hope that makes sense. Ian http://examples.roughian.com 2009/12/18 zizou84 <arous.ri...@gmail.com> > hi > i began with gwt and i had a difficulty to understand this expression: > "In GWT, all state is purely client-side. A GWT application could be > opened multiple times in multiple browsers, and each window would > essentially have its own instantiation of the application. Hence each > window could be in any state the user wishes, and there is no state > conflict. More, the server need not even be aware of the number of > client windows that are open; each window communicates with largely > stateless server services, and the server is not tasked with tracking > more state due to more interactions with a single client. " > what does mean :" A GWT application could be opened multiple times in > multiple browsers, and each window would essentially have its own > instantiation of the application" > and what is the difference in this point between a GWT application and > a web application > > -- > > You received this message because you are subscribed to the Google Groups > "Google Web Toolkit" group. > To post to this group, send email to google-web-tool...@googlegroups.com. > To unsubscribe from this group, send email to > google-web-toolkit+unsubscr...@googlegroups.com<google-web-toolkit%2bunsubscr...@googlegroups.com> > . > For more options, visit this group at > http://groups.google.com/group/google-web-toolkit?hl=en. > > > -- You received this message because you are subscribed to the Google Groups "Google Web Toolkit" group. To post to this group, send email to google-web-tool...@googlegroups.com. To unsubscribe from this group, send email to google-web-toolkit+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-web-toolkit?hl=en.
