Le vendredi 04 f�vrier 2005 � 12:18 +0100, Erik Bruchez a �crit :
> Simple: there is no caching.
Simple indeed!
Can I suggest two possible strategies that would improve things without
being too difficult to implement?
The first one would be to provide a timeout parameter associated with
the XQuery request that would define the expected validity of the query.
Of course, that could create a delay between the moment an update is
done on the DB and the moment it shows out on the site, but when the
update rate is low that could be acceptable.
The second one would be to store, for each collection, the timestamp of
the last update and to use that information to manage the cache. That
would be reliable for databases that are not updated directly (out of
the control of Presentation Server) such as embedded eXist databases.
Do you think these options would be worth RFEs?
Thanks,
Eric
--
Curious about Relax NG? Read my book online.
http://books.xmlschemata.org/relaxng/
------------------------------------------------------------------------
Eric van der Vlist http://xmlfr.org http://dyomedea.com
(ISO) RELAX NG ISBN:0-596-00421-4 http://oreilly.com/catalog/relax
(W3C) XML Schema ISBN:0-596-00252-1 http://oreilly.com/catalog/xmlschema
------------------------------------------------------------------------
-------------------------------------------------------
This SF.Net email is sponsored by: IntelliVIEW -- Interactive Reporting
Tool for open source databases. Create drag-&-drop reports. Save time
by over 75%! Publish reports on the web. Export to DOC, XLS, RTF, etc.
Download a FREE copy at http://www.intelliview.com/go/osdn_nl
_______________________________________________
orbeon-user mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/orbeon-user
