Apr 5th, 2012, 04:20 PM
Webflow populates previous session state when opening new tab/window
I have worked to integrate webflow into an existing spring MVC portal application primarily for its conversational support but after spending all this time re-engineering I am getting an adverse reaction from the end user. Webflow seems to do everything i was looking for as far as allowing the end user to use the application in multiple browser tabs/windows. The only issue seems to be what happens when opening the new tab/window or refreshing the page (all http GETs)
The percieved "problem" is described as follows:
A user performs a search on page 'A', normal results are returned.
The user then opens a new tab/window and puts in the url to the same search page. (any http GET)
when the page loads it is populated with the search results from page 'A' rather than a blank search page.
It looks to me like this is all managed via webflow and I dont see a good way to change this behavior.
Has anyone run into this? I don't personally find this to be an issue but the end user is pushing this.
Maybe I am missing something?
Any help would be appriciated...
Apr 6th, 2012, 01:12 AM
Thats the way the browser works.. It isn't a new session it is the same session.. Only opening a REAL new browser will help you, opening a new tab of opening a new browser window from the current copies all the session state to the new tab/window. Also what you see is the behavior of spring webflow because of the post-redirect-get and the get can be issued multiple times with the same result.
You could disable this but that also destroys proper back button support.
Apr 9th, 2012, 10:14 AM
So my take away from this is that it's a limitation of stateful web applications and perhaps by extention webflow as well? Again, I do not see this as a catastrophic problem, more like a training issue at worst. Webflow solved the problem with mutliple tab/window support, I believe this is pushback from an end user who is exceptionally averse to change.