RE: Visit object or use persistent="yes" . Need reference implementation

[hari ks <ha...@yahoo.com>]

Thanks. That clarified many things.
Does that mean Visit object need to always act as
facade to domain objects. For applications that have
pages that keep on growing, how do we manage these. 
What is a reference implementation for tapestry?
Can betterpetshop project be taken as refernce?
Or any of the examples that come with tapestry
distribution?
Thanks,
Hari

--- Patrick Casey <pa...@adelphia.net> wrote:

> 
> 	Tapestry persistent properties are linked to a
> specific page, not to
> a session.
> 
> 	So if you log in on page "Login" and persist
> "currentUser" it won't
> be available on page "welcomeScreen" because it's
> only persisted to the
> Login page.
> 
> 	An additional limitation is that persistent
> properties aren't
> associated with a specific page instance, but rather
> with a page/session
> combination. Thus if a given session brings up two
> copies of the same page,
> their persistent properties will overwrite one
> another.
> 
> 	Generally speaking if you want information to have
> global scope e.g.
> be available on more than one page, stash it in the
> visit object (which then
> goes in the session), or put it in the session
> yourself.
> 
> 	--- Pat
> 
> > -----Original Message-----
> > From: hari ks [mailto:hari_tcs@yahoo.com]
> > Sent: Monday, August 22, 2005 12:54 AM
> > To: tapestry-user@jakarta.apache.org
> > Subject: Visit object or use persistent="yes" of
> property-specificaion
> > (TIA). Also need tapestry coding standards.
> > 
> > Hi,
> >    In tapestry in action - hangman application, a
> > user's state is stored in Visit object
> > (Game/WordSource are inside Visit). Visit acts as
> > facade for Game & WordSource.
> >    Is this always the way we should code our
> tapestry
> > application.
> > Or can we also use persistent="yes" directly in
> > property-specification of a page to maintain user
> > state for a session.
> > 
> > What would be the drawbacks of using
> persistent="yes"
> > for lots of properties in a page.
> > 
> > Also I presume eliminating instance variables is
> not
> > completely possible in tapestry page because
> > components like Foreach,ListEdit etc.. would need
> > them.  But new developer starts using instance
> > variables to store user state between request
> causing
> > possible security breach because of caching. Is
> there
> > any coding standards defined for Tapestry
> anywhere?
> > Want to implement the tapestry coding standards in
> our
> > project.
> > 
> > Thanks,
> > Hari
> > 
> > 
> > 
> >
> ____________________________________________________
> > Start your day with Yahoo! - make it your home
> page
> > http://www.yahoo.com/r/hs
> > 
> > 
> >
>
---------------------------------------------------------------------
> > To unsubscribe, e-mail:
> tapestry-user-unsubscribe@jakarta.apache.org
> > For additional commands, e-mail:
> tapestry-user-help@jakarta.apache.org
> 
> 
> 
> 
>
---------------------------------------------------------------------
> To unsubscribe, e-mail:
> tapestry-user-unsubscribe@jakarta.apache.org
> For additional commands, e-mail:
> tapestry-user-help@jakarta.apache.org
> 
> 


__________________________________________________
Do You Yahoo!?
Tired of spam?  Yahoo! Mail has the best spam protection around 
http://mail.yahoo.com 

---------------------------------------------------------------------
To unsubscribe, e-mail: tapestry-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tapestry-user-help@jakarta.apache.org