Sometimes, it is nice to clear the page recorders for a set of pages prior
to the session expiring (starting a "new order" for instance)...how are
folks doing this?


----- Forwarded by Christian Hall/Technology/Equifax on 07/18/2002 12:02 PM
-----
|--------+---------------------------------------------->
|        |          "Howard M. Lewis Ship"              |
|        |          <[EMAIL PROTECTED]>                  |
|        |          Sent by:                            |
|        |          [EMAIL PROTECTED]|
|        |          eforge.net                          |
|        |                                              |
|        |                                              |
|        |          07/18/2002 11:43 AM                 |
|        |                                              |
|--------+---------------------------------------------->
  
>------------------------------------------------------------------------------------------------|
  |                                                                                    
            |
  |      To:     "Tom Davies" <[EMAIL PROTECTED]>                             
            |
  |      cc:     <[EMAIL PROTECTED]>                            
            |
  |      Subject:     Re: [Tapestry-developer] StaleLink Problem                       
            |
  
>------------------------------------------------------------------------------------------------|




About persistent page properties:

Tapestry is a little bit like a time sharing system.  When you code sees a
page instance, Tapestry has filled in the persistent properties with values
previously stored for your session.  It is maintaining the illusion that
the
page exists just for your session.

The reality is that the page instances are pooled and shared between
sessions.  There are endless variations, but basically you need to count on
the fact that between request cycles, you will get two different page
instances.  In fact, when (in development mode) you turn caching off, you
always get a fresh instance of a page on each request cycle.

Your code doesn't know this; it just knows that the parts that count, the
persistent page properties, are the same request cycle to request cycle
(because those few values are, in fact, stored in the HttpSession between
request cycles).

----
Howard Lewis Ship
[EMAIL PROTECTED]
http://tapestry.sf.net



----- Original Message -----
From: "Tom Davies" <[EMAIL PROTECTED]>
Cc: <[EMAIL PROTECTED]>
Sent: Friday, July 12, 2002 10:00 PM
Subject: Re: [Tapestry-developer] StaleLink Problem


> On Sat, 2002-07-13 at 12:25, Howard M. Lewis Ship wrote:
> > The problem is that you have to understand a lot about Tapestry to get
it to
> > work right; other than that, it's fine (speed is not an issue).  But
the
> > concept of repeatable renders (which, in turn, is which properties must
be
> > persistent so as to re-render the page a second time), it difficult to
> > express.
>
> I use Action extensively, and so far it seems to work, but I'll admit
> that I don't understand the finer points of persistent properties -- in
> fact I don't even understand why there is a distinction -- is it to do
> with a single page instance being used by several sessions?
>
> How can one use Direct as a substitute for Action? The only way I can
> see to do that is to maintain my own Map of keys and listeners.
>
> Tom
>
> --
> "Optimism is a duty. The future is open. It is not predetermined. No one
> can predict it, except by chance. We all contribute to determining it by
> what we do. We are all equally responsible for its success."
>   Karl Popper
>
>
>
> -------------------------------------------------------
> This sf.net email is sponsored by:ThinkGeek
> Welcome to geek heaven.
> http://thinkgeek.com/sf
> _______________________________________________
> Tapestry-developer mailing list
> [EMAIL PROTECTED]
> https://lists.sourceforge.net/lists/listinfo/tapestry-developer
>



-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
_______________________________________________
Tapestry-developer mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/tapestry-developer



Protect yourself against identity theft with Equifax Credit Watch. Visit
http://www.creditalert.equifax.com.

This message contains information from Equifax Inc. which may be
confidential and privileged.  If you are not an intended recipient, please
refrain from any disclosure, copying, distribution or use of this
information and note that such actions are prohibited.  If you have
received this transmission in error, please notify by e-mail
[EMAIL PROTECTED]



-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
_______________________________________________
Tapestry-developer mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/tapestry-developer

Reply via email to