You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@tapestry.apache.org by "Dimm, Jason" <ja...@cingular.com> on 2006/02/20 16:51:07 UTC

Visit Object

How do you definitively find out if your Tapestry application's Visit object
really is per user?

Are their any weird circumstances in which it would be shared?

 

Thanks,

 

Jason E. Dimm, Senior Analyst, Cingular Wireless
IT eCommerce/Payments (Payment Processing)

Cingular Java Components, QuickPay, Wedat
Sun Certified Java Developer

Sun Certified Java Programmer
12555 Cingular Way
Alpharetta, GA 30004
Office (678)893-2232
as� es la vida.

RE: Visit Object

Posted by James Carman <ja...@carmanconsulting.com>.
If you’re using Tapestry 4 (and you should be), then you can specify a
“scope” for your Application State Objects (ASOs).  Other than that, the
“visit” object in Tapestry 3 is definitely session-scoped.  The “global”
object is the servlet context-scoped object.

 

  _____  

From: Dimm, Jason [mailto:jason.dimm@cingular.com] 
Sent: Monday, February 20, 2006 10:51 AM
To: 'tapestry-user@jakarta.apache.org'
Subject: Visit Object

 

--> 

How do you definitively find out if your Tapestry application's Visit object
really is per user?

Are their any weird circumstances in which it would be shared?

 

Thanks,

 

Jason E. Dimm, Senior Analyst, Cingular Wireless
IT eCommerce/Payments (Payment Processing)

Cingular Java Components, QuickPay, Wedat
Sun Certified Java Developer

Sun Certified Java Programmer
12555 Cingular Way
Alpharetta, GA 30004
Office (678)893-2232
así es la vida.