3. In the ajax client only html is send to the client.
4. The selection is send to the server which recalculates the charts and the webpage is refreshed in the ajax client
5. Each user will get a session in which selection states and such are kept, separate from other users. The server will maintain only one copy of the qvw document in RAM. So each user adds some RAM overhead to that needed for the qvw document itself.
6. The user session will end.
7. The ajax client will only show the html page that was send by the server. It will not need to load any other data than what is necessary to render the html page on screen. All the calculations are done on the server.