EDIT: More detail here. Basically if you
1. open a tab1 to url1 (GET request which may save url in session)
2. open a tab2 in another url2 (GET request which save url in session overwriting 1)
3. go back to tab1, and click add project which issues GET request to get post form
4. when posting now, it will go back to tab2 incorrectly when it should go back to tab1 since that is where we choose "create new issue" link from.
This behavior pretty much is very confusing to the user. As web developers, we want to be able to add an add project button on any page in our application, but that results in the above type of bugs consistently which is very annoying.
The main question of this post is WHAT are others doing for tab/conversation state? Read through the example below as well.
We have been porting from seam....while the conversations where semi nice, we almost really wanted tab state. The more we analyzed this, the more we understood why no tab state exists.
We could create a tabid=xxxx where xxx is a guid, but in playframework, when would you time that out. If the network went down, you would never know that it times out. tabid would then tie back to a cookie with the name xxxx for that domain so you have tab state.
You could put the tabids in the session cookie every time so that you could eventually time out the tabs....not a bad idea really. would be nice if play already had something like this. If a user had stuff open to long, it would end the tab state...would need to save timestamps of last request from that tab which had the tabid param in it.
For now, we are going with ajax popping of forms so if someone is adding a ticket, and they pulldown the projects menu and choose new project, we stay on the page and ajax popup a form....not sure how this will work.
Our main goal is really we always want to go back to the url that the user came from and be able to add edit/add buttons to any page and not worry about getting back to the page the user came from....the only way I can think of doing that is ajax popping up BUT that has a really big disadvantage of NO referencable urls.
EXAMPLE: We have edit project, ideally a user can go straight to the url of the edit project url which has the project name in the url!!! but then we can't get back to the url they came from, OR we can do ajax form popup BUT then we can't have a nice url that can be passed around to view/edit the project(mostly view).
What are other people's thoughts on this? Which direction to take? We prefer not to have a read project page and edit project page and just have one edit project page that most people just read and sometimes edit.
thanks, Dean
