I have never come across such a problem either, and we have done a lot of testing for this. Your problem sounds like it has little to do with the session and more to do with page pooling, i.e.: how you initialize your pages. The golden rule there is that your fields must always be private, and then should be referenced by public accessors, having a public field in a page is like using a static variable which may explain your problem.
-- If you are not an intended recipient of this e-mail, please notify the sender, delete it and do not read, act upon, print, disclose, copy, retain or redistribute it. Please visit http://www.albourne.com/email.html for important additional terms relating to this e-mail. ----- Original Message ----- From: [EMAIL PROTECTED] To: users@tapestry.apache.org Sent: Monday, 20 October, 2008 2:53:17 PM GMT +02:00 Athens, Beirut, Bucharest, Istanbul Subject: Re: "Session bleedings" in Tapestry5 I quote from a chat protocol with a developer: "Take for eg, if there are 10 users at present using our website, then first user clicks on 1st page, and 5th user clicks on 2nd page, and 3 rd person clicks on 3 page and using it. And if the user 1 is clcked on 8 page at that time user 3 want to goto another page say 5, then he also gets 8 instead of 5. As first user requested that page. :( " -------- Original-Nachricht -------- > Datum: Mon, 20 Oct 2008 13:32:16 +0200 > Von: Tobias Wehrum <[EMAIL PROTECTED]> > An: Tapestry users <users@tapestry.apache.org> > Betreff: Re: "Session bleedings" in Tapestry5 > Hello namesake, > > Since I've never heared about this too, I searched the Mailing List and > JIRA and didn't find any issue which you could've meant. > Where did you hear that? > > - Tobias > > [EMAIL PROTECTED] schrieb: > > I have heard there are some issues with "Session bleedings" in > Tapestry5. > > > > Will those issues be fixed by November? > > > > I would like to go live with a T5 application by November/December.... > > > > Thanks! > > > > Tobias > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > For additional commands, e-mail: [EMAIL PROTECTED] > > > > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
