Do they use javascript to detect they are in a freshly created window? Do
windows natively have an id that can be used in the conversation id?
JumpStart's wizard solution lets you open more than one window and run a wizard
in each window - it is the act of entering the wizard that starts a uniqu
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 c
Moritz,
some time ago I read a bit about JBoss Seam and I think it solves the
"session per window" problem. Maybe the solution could be adapted to be used
by Tapestry applications.
Sincerely,
Matheus Eduardo Machado Moreira
matheus@gmail.com
"Violence is the last refuge of the inco
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
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
Hi,
Does anybody know of a practicle way to handle the situation that a user opens
multiple browser windows and does persistant changes in one window that will of
course be reflected in the session of the other window too since both windows
share the same session (as long as it is the same brow
