I agree that one should try to defer session creation as long as possible. But as soon as there is some state to persist, you shouldn't hesitate to use sessions.
Session replication isn't necessarily a heavy thing. Have a look at Terracotta, which shines at making web session replication scale well. Combine this with sticky sessions, and you get the best of two worlds. Terracotta does only send replicated data to the nodes that actually demands it. See http://www.terracotta.org Olle Hallin Senior Java Developer and Architect olle.hal...@crisp.se www.crisp.se http://www.linkedin.com/in/ollehallin 2010/1/7 Thiago H. de Paula Figueiredo <thiag...@gmail.com> > Em Wed, 06 Jan 2010 13:36:31 -0200, Jim O'Callaghan <jc1000...@yahoo.co.uk> > escreveu: > > > Thanks for the responses Thiago. >> > > You're welcome! > > I'll have a look at the >> LinkCreationListener you suggested in your other email. Regarding the >> response below, does the approach not make an assumption that the objects >> I am trying to share between pages are persisted objects with a >> key(id)/value elationship? I'm using something at the moment that manages a >> menu stack in the user's session and some other data that is really just >> relevant to >> >> the user's session and not something I had thought of persisting. >> > > The approach doesn't assume your objects have an id, but it does assume you > won't put much information in the URLs. Internet Explorer, for example, has > a limit of 2083 characters. > > -- > Thiago H. de Paula Figueiredo > Independent Java, Apache Tapestry 5 and Hibernate consultant, developer, > and instructor > Owner, software architect and developer, Ars Machina Tecnologia da > Informação Ltda. > http://www.arsmachina.com.br > > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org > For additional commands, e-mail: users-h...@tapestry.apache.org > >
