You certainly have to set up the visit data to be java.io.Serializable as your first step.
Joel
-----Original Message-----
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]]
Sent: Saturday, March 22, 2003 2:20 PM
To: [EMAIL PROTECTED]
Subject: Tapestry-developer digest, Vol 1 #576 - 1 msg
Send Tapestry-developer mailing list submissions to
[EMAIL PROTECTED]
To subscribe or unsubscribe via the World Wide Web, visit
https://lists.sourceforge.net/lists/listinfo/tapestry-developer
or, via email, send a message with subject or body 'help' to
[EMAIL PROTECTED]
You can reach the person managing the list at
[EMAIL PROTECTED]
When replying, please edit your Subject line so it is more specific
than "Re: Contents of Tapestry-developer digest..."
Today's Topics:
1. distributed environment (Eric Schneider)
--__--__--
Message: 1
From: "Eric Schneider" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Date: Fri, 21 Mar 2003 16:51:09 -0500
Subject: [Tapestry-developer] distributed environment
Hi all,
So, we're getting ready to deploy one of our applications in production.
This happens to be the first tapestry application that is stateful. Our
client is planning to run the application on three separate app servers, all
running sun's sunone server.
The application is currently running on all of the machines. The web server
is setup to round robin requests to the 3 app servers. If a requests are
routed to alternate app servers other than the server their visit was
created on, we get the session timeout page. We can set up the web server
to use a sticky approach, but we'd like to avoid that if we can.
Can someone point me to some documentation on setting up tapestry apps in a
distributed environment?
Thanks in advance.
eric.
--__--__--
_______________________________________________
Tapestry-developer mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/tapestry-developer
End of Tapestry-developer Digest
