Hi,dear all!
I sometime use @Persist annotation to make object store in session.
such as:
public class PageNav2 {
@Persist("session")
@Property
private Paging paging;
@SetupRender
void onLoad(){
if (paging==null)
paging = new Paging();
}
...
}
In modern browsers,multiple page tab is very popular.
In firefox or google chrome,if I opened one page with some object
saved in session,and then open the same page in new page tab.
The object which I created in first time would be shared to second page.
When we use tapestry at e-business or e-commerce application,there
will raising problem with re-submit or breaking data consistency.
Because client can visit same object of session to modify its status
in many time via multiple page tab.
Which kind of method can fix it?
Change to give up session at this occasion,instead of using form-post
necessary data?
Or we have a way like Jboss Seam's conversation to manage session?
--
cleverpig(Dan)
Location: Beijing
Address: Room 4018,No.A2 South Avenue Fuxingmen Beijing,P.R.China
Zipcode: 100031
MSN: great_liu...@hotmail.com
QQ: 149291732
Skype: cleverpigatmatrix
Facebook ID:cleverpig
Blog: cleverpig.name/dan/
Tags: del.icio.us/cleverpig
Twitter: twitter.com/cleverpig
新浪微博: t.sina.com.cn/cleverpig
Organization: www.beijing-open-party.org
or...@facebook: http://www.facebook.com/group.php?gid=8159558294
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org
For additional commands, e-mail: users-h...@tapestry.apache.org
