Regarding Tynamo's conversations, that's technically correct but the driving principle is "many small conversations rather than one big one". For a shopping cart, I'd certainly argue that to implement it properly, the state of a shopping cart needs to be stored in a database. Of course, the right conversational type in practice depends on your exact use case.
Kalle On Tue, May 25, 2010 at 8:16 AM, Geoff Callender <geoff.callender.jumpst...@gmail.com> wrote: > Tynamo favours a conversation in a single page. If you need a conversation > across multiple pages then have a look at: > > > http://jumpstart.doublenegative.com.au/jumpstart/examples/wizard/usingpages1 > > Geoff > > On 26/05/2010, at 12:22 AM, Thiago H. de Paula Figueiredo wrote: > >> Take a look at >> http://communitymapbuilder.org/display/TYNAMO/tapestry-conversations+guide. >> >> -- >> Thiago H. de Paula Figueiredo >> Independent Java, Apache Tapestry 5 and Hibernate consultant, developer, and >> instructor >> Owner, 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 >> > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org > For additional commands, e-mail: users-h...@tapestry.apache.org > > --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org For additional commands, e-mail: users-h...@tapestry.apache.org
