you could set up a cookie to carry a transaction Id.
but you have to remember to time out your transaction if the user closes his browser
for example.
also, if you plan to have a transaction span more than one HTTP request,you are also
holding resources for that transaction. Hence your scalability will go down, because
you are no dependent on the user and how fast he/she commits the transaction.
Try to keep your transaction only span one request for best performance
Filip
-Original Message-
From: Fabio Mengue [mailto:[EMAIL PROTECTED]]
Sent: Tuesday, February 18, 2003 9:43 AM
To: Tomcat Users List
Subject: [OT] Transaction
Hi,
Anybody know if it is possible to share a transaction context between
all levels of my system ?
I explain: today I am able to start a transaction between my servlet
(inside Tomcat) and the database. Is it possible to "expand" this
transaction to the client browser ? Do I need to write an applet for
that or a fat client ?
In fact, do I make sense at all ? :)
Thanks a lot,
F.
--
Fabio Mengue - Centro de Computacao - Unicamp
[EMAIL PROTECTED] [EMAIL PROTECTED]
Furious activity is no substitute for understanding. H.H. Williams
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
