[plt-scheme] correctness of capturing continuations in servlets

I don't have a general purpose solution integrating transactions into 
the language,
as Shriram points out.

For now, you might be able to make do by procrastinating any updates to 
the
database until the end.  At that point, use either send/finish or 
send/forward
to disable going back.  You may need to check that none of the data 
accessed
when constructing the previous pages has changed by the time the update 
happens.
My ESOP2003 paper gives an example of what can happen if state becomes 
out
of date yet remains undetected.
   http://www.ccs.neu.edu/scheme/pubs/#esop2003-gfkf

Paul
On Thursday, April 24, 2003, at 11:23 PM, Alexander Boldakov wrote:

>   For list-related administrative tasks:
>   http://list.cs.brown.edu/mailman/listinfo/plt-scheme
>
>   For list-related administrative tasks:
>   http://list.cs.brown.edu/mailman/listinfo/plt-scheme
>
>
> Hello!
>
> How do I handle the situation like the following in PLT Web server.
>
>  Let suppose that servlet works with some external resourses,
>  for example with database. We capture continuation somewhere
>  in the middle of transaction with send/suspend function. Then
>  we restore this continuation (may be several times) and make
>  some actions. I want to find out how to provide correctness
>  in this situation.
>
> BTW, I'm looking for papers on the subject. Can you advice me some?
>
> -- 
> Best regards,
>        Alexander