that sounds like a doable solution as, when i researched more into the
redirects indeed it seems really messy, my only question about passing the
information into a temp DB, would be how could we refrence between two
sessions to share the stored data. Doesn't each session have a unique ID?
a lil more about our project. Its a large scale ecommerce site, that will
have many thousand concurrent users, i think having a DB that is in-memory
only would not create a bottle neck issue, as that seems equilivant to passing
system messages, since the data is being kept in the RAM neways.
again my only concern is how we can link up the sessions within that DB.
thanx alot for the advice
evan rawson
Richard Clark <[EMAIL PROTECTED]> wrote:
On Nov 17, 2005, at 16:10, evan rawson wrote:
> Hiya we have a quite large tapestry application we are developing
> and was wondering if and how we could share httpsession data
> between tapestry applications.
I would extract the data and stuff it into a common database that is
then accessed by the two applications. You could use Hibernate SQL in
its "in-memory" configuration if you needed speed and don't need to
hold the data across a restart.
Trying to pass data back and forth using a RedirectException sounds
messy, and all those redirections will slow down the application.
...Richard
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------
Yahoo! FareChase - Search multiple travel sites in one click.
