This looks very promising to achive one of the design goals for our application. The designers want to be able to open multiple concurrent browser windows and have them basically be separate instances.
I'm afraid that one thing stands in the way however. Another requirement is that the browser back/forward buttons work in the application. To do this, we are using the ThreadBookmark to set the browser history. When I did some testing yesterday with two Firefox browser windows, I found that they stepped on each other's browser history. I am assuming that there is only one ThreadBookmark queue per session, so both browser instances were using the same queue. Is that a correct assumption? If so, will the ForcePageInstance help in this case?
EDIT: Palli, I did some further testing and it seems that the back/forward buttons are OK when using multiple windows. The only problem I ran into is when I clicked the browser back button and left my VWG application. For example, if I bring up a new browser window it goes to our intranet page. I enter the URL for our application in the window and bounce around. If I use the back button all the way to the home page, then back again to our intranet page, the forward buttons then do not go to the proper place. That is only a minor annoyance. I just wanted to let you know the new things I found and see if this matches what your experience has been in the past.