RE: Best place to syncronize within struts.

2003-03-03 Thread Jacob Hookom
Synchronization should take place at the lowest denominator possible.
The other thing to do is create a caching filter for your web content
that stores the page for 2-5 minutes before it refreshes itself.

-Original Message-
From: Simon Kelly [mailto:[EMAIL PROTECTED] 
Sent: Monday, March 03, 2003 8:47 AM
To: Struts Users Mailing List
Subject: Best place to syncronize within struts.

Hi,

During my struts app I have to gather a large amount of data from an
Oracle
db (4-40MB each hit).  I was wondering, as the site will be accessed at
regular intevals of about 2-5 minutes by upto 50 people at a time, what
would be the best place to sycronize the code to make sure that the
access
time is kept to as short a time period as possible?

Regards

Simon



Institut fuer
Prozessdatenverarbeitung
und Elektronik,
Forschungszentrum Karlsruhe GmbH,
Postfach 3640,
D-76021 Karlsruhe,
Germany.

Tel: (+49)/7247 82-4042
E-mail : [EMAIL PROTECTED]


-
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]



Re: Best place to syncronize within struts.

2003-03-03 Thread Simon Kelly

- Original Message -
From: "Jacob Hookom" <[EMAIL PROTECTED]>
To: "'Struts Users Mailing List'" <[EMAIL PROTECTED]>
Sent: Monday, March 03, 2003 3:55 PM
Subject: RE: Best place to syncronize within struts.


> Synchronization should take place at the lowest denominator possible.

By this I take it you mean as close to the actual call to the db as
possible?

> The other thing to do is create a caching filter for your web content
> that stores the page for 2-5 minutes before it refreshes itself.

In the whole application the data will be entering the db every 5 seconds or
so from the other end so caching may cause some critical data to be missing
from any given access.

Thanks for the info though, I will look into both of them.

Cheers

Simon


>
> -
> 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]
>
>


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



Re: Best place to syncronize within struts.

2003-03-03 Thread Ivan N. Zhidov
You may consider using JCS, I've done some research into for a project but
never actually used it. It's caching mechanism and it will allow you to
specify the in-memory size and expiration on your data.

Cheers,
Ivan
- Original Message -
From: "Simon Kelly" <[EMAIL PROTECTED]>
To: "Struts Users Mailing List" <[EMAIL PROTECTED]>
Sent: Monday, March 03, 2003 10:00 AM
Subject: Re: Best place to syncronize within struts.


>
> - Original Message -
> From: "Jacob Hookom" <[EMAIL PROTECTED]>
> To: "'Struts Users Mailing List'" <[EMAIL PROTECTED]>
> Sent: Monday, March 03, 2003 3:55 PM
> Subject: RE: Best place to syncronize within struts.
>
>
> > Synchronization should take place at the lowest denominator possible.
>
> By this I take it you mean as close to the actual call to the db as
> possible?
>
> > The other thing to do is create a caching filter for your web content
> > that stores the page for 2-5 minutes before it refreshes itself.
>
> In the whole application the data will be entering the db every 5 seconds
or
> so from the other end so caching may cause some critical data to be
missing
> from any given access.
>
> Thanks for the info though, I will look into both of them.
>
> Cheers
>
> Simon
>
>
> >
> > -
> > 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]
> >
> >
>
>
> -
> 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]