Re: AJAX, XML and Caching(?)
- From: Bart Van der Donck <bart@xxxxxxxxxx>
- Date: Fri, 18 Jan 2008 05:24:08 -0800 (PST)
Thomas 'PointedEars' Lahn wrote:
Mariano wrote:
what can i do if I wanna have a DB load lighter than before???.
And the answer is simple: you need a *server-side indicator* about whether
or not the database (or database table) was changed in the meantime. Only
if it was changed you make a new query, regardless how many requests are
coming in. Caching the query in an XML file server-side (I suppose that is
what Bart suggested; again, you have not quoted anything relevant) would be
a good idea.
In this case I think it's best to update the XML-file only when the
database is actually modified, e.g. in same program just after the SQL-
command(s). The read-actions can then still use a static XML-file
rather than going to the database all the time. This approach should
result in a considerable speed improvement especially on heavy-duty
systems.
(OP -> Watch out for possible read/write locks of the Operating
System)
--
Bart
.
- Follow-Ups:
- Re: AJAX, XML and Caching(?)
- From: Thomas 'PointedEars' Lahn
- Re: AJAX, XML and Caching(?)
- References:
- AJAX, XML and Caching(?)
- From: Mariano
- Re: AJAX, XML and Caching(?)
- From: Bart Van der Donck
- Re: AJAX, XML and Caching(?)
- From: Mariano
- Re: AJAX, XML and Caching(?)
- From: Thomas 'PointedEars' Lahn
- AJAX, XML and Caching(?)
- Prev by Date: Re: Image pop up
- Next by Date: Re: FireFox: event handling problem
- Previous by thread: Re: AJAX, XML and Caching(?)
- Next by thread: Re: AJAX, XML and Caching(?)
- Index(es):
Relevant Pages
|
