Have you considered storing the XML in an XML db like eXist?
- Thomas.
[EMAIL PROTECTED] wrote:
thnx rof your hints but
the problem is that i dont want to chache the xsp but the xml content that
xsp generate. The XSP run a esql query and produce a 7000-10000 nodes xml
i want to avoid runing the xsp (java) code again and again
-- stavros
On Thu, 20 May 2004, Joerg Heinicke wrote:
On 19.05.2004 13:37, iyy wrote:
use caching.
http://server:8080/cocoon/docs/userdocs/concepts/caching.html
Caching is the way to go. You can either make your XSP cacheable (e.g.
by using ExpiresValidity) or configure the pipeline to be cacheable
("expires 1 hour" or similar).
Dotring such a huge XML tree in session will probably lead fast to an
OutOfMemoryError.
Joerg
i have a .xsp that read from a database and create a .xml file that
describe a tree, then the data from this xml are transformed to a
javascript tree
the problem is that i need the xml data from the database in each request
to create the tree (navigation tree) but some times those data produce a
.xml with 7000 - 10000 nodes. so i have to wait some minutes to ge a
responce.
my question is:
where can i store temporary the produced XML (i can not use file system)
so not to have to call .xsp in each request?
is it possible to store the tree in SESSION ?
WriteDOMSessionTransformer should be your friend:
---------------------------------------------------------------------
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]
