[Seaside] WATransaction & WATransactionStack?

[Stephen Pair]

Hmmm...I must have an outdated version then.  I don't have
WATransactionTest, and I can find any place that makes use of
WATransaction and WATransactionStack (other than isolate and places that
hold the current transaction).

Looks like I'm on 2.15.  Looking at the website, it appears that there
is a 2.2.  Did I miss an announcement (I was temporarily not receiving
some of the email posted to the Seaside list)?

Do you have a synopsis of the changed made in 2.2?

- Stephen

> -----Original Message-----
> From: seaside-bounces at lists.squeakfoundation.org 
> [mailto:seaside-bounces at lists.squeakfoundation.org] On Behalf 
> Of Avi Bryant
> Sent: Friday, January 31, 2003 4:52 PM
> To: The Squeak Enterprise Aubergines Server - general discussion.
> Subject: Re: [Seaside] WATransaction & WATransactionStack?
> 
> 
> 
> On Fri, 31 Jan 2003, Stephen Pair wrote:
> 
> > How are these classes used?  In looking at the system, it's not 
> > apparent to me that these classes are used at all.  Are 
> these a left 
> > over from when you were doing more implicit management of 
> the state of 
> > WAComponents?
> 
> No, they have nothing to do with that.  They are used in the 
> implementation of WASession>>isolate:.  There's an example 
> use (in recent releases anyway) in the WATransactionTest 
> (registered under /seaside/txn).
> 
> The idea is that if you put code inside an #isolate: block, 
> any pages created during that block will immediately expire 
> as soon as the block ends.  I use this, for example, to 
> surround an entire sale in a point-of-sale application: once 
> payment has been received, you're not allowed to use the back 
> button to modify the contents of the shopping cart...
> 
> Avi
> 
> _______________________________________________
> Seaside mailing list
> Seaside at lists.squeakfoundation.org
> http://lists.squeakfoundation.org/listinfo/seaside
>