Mailing-List: contact jcs-users-help@jakarta.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "JCS Users List" <jcs-users@jakarta.apache.org>
Received-SPF: pass (asf.osuosl.org: domain of Aaron.Smuts@travelocity.com
 designates 151.193.220.19 as permitted sender)
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Subject: RE: How to implement write-thru caching with JCS?
Date: Mon, 25 Jul 2005 09:47:51 -0500
Message-ID: 
 <F117F441A30ACD42A50F285320C40E613C47DA@sgtulmsp04.Global.ad.sabre.com>
Thread-Topic: How to implement write-thru caching with JCS?
Thread-Index: AcWQvcmCAHWA/3PhT8G0pnMQ3NzZbAAaRzhQ
From: "Smuts, Aaron" <Aaron.Smuts@travelocity.com>
To: "JCS Users List" <jcs-users@jakarta.apache.org>,
	"Prasad xyz" <pvjava@gmail.com>

It's not perfectly clear to me what you're asking.  In any case, it
looks like you have too much code in your jsp pages, which in my
experience leads to big problems.  Why don't you create a common data
access layer and control the caching there.  When you add records you
can invalidate related cache entries, etc.  If you follow an MVC pattern
then you would probably already have such a layer.  Given your current
code, can't you just clean up whatever lists jsp1 uses in jsp2?

Aaron


> -----Original Message-----
> From: Prasad xyz [mailto:pvjava@gmail.com]
> Sent: Sunday, July 24, 2005 10:08 PM
> To: jcs-users@jakarta.apache.org
> Subject: How to implement write-thru caching with JCS?
>=20
> Hi folks,
>=20
> I have a simple jsp which displays a really huge table (10k+ rows),
> the jsp just invokes a bean which does all the query execution and
> populates & returns an arraylist based on the resultset object:
>=20
> //this is within jsp1
> <jsp:useBean id=3D"display" class=3D"reports.Database" />
>=20
> <%
> //this method executes the query and
> populates & returns an arraylist object
> ArrayList result =3D display.showTable();
> %>
>=20
> //loop thru the arraylist to render the table
>=20
> <TABLE BORDER=3D2>
> <%
> for(int i=3D0; i<result.size(); i++) {
> 	out.println(((StringBuffer)result.get(i)).toString());
> }
> %>
> </TABLE>
>=20
> I am planning to use JCS to cache the arraylist object so that I avoid
> issuing a fresh query everytime a user hits jsp1.
>=20
> I also have another jsp which writes to the same table, so the
underlying
> table is modified every time a user inputs data using the other jsp
(jsp2)
>=20
> My question is - how would I do write-thru caching in this scenario?
> if a user hits jsp1 and the arraylist object is cached, then user goes
> to jsp2 and updates some data, I want the cache to realise that the
> underlying table got modified and dynamically refresh the cached
> arraylist object by calling display.showTable(), so now when the
> user goes back to jsp1 then the updated data is instantly served
> from the cache, is it possible to do something like this in JCS?
>=20
> I would appreciate any help on this, thanks in advance!
>=20
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: jcs-users-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: jcs-users-help@jakarta.apache.org

---------------------------------------------------------------------
To unsubscribe, e-mail: jcs-users-unsubscribe@jakarta.apache.org
For additional commands, e-mail: jcs-users-help@jakarta.apache.org