You cannot easily detect that just from these examples. I do see
references to com.xhive.dom.*. Ideally the X-Hive DOM is a
specialization of the W3C DOM. Besides, the way access is provided to
the actual document is purely technical. It should not matter to you
whether the DOM you get actually resides in memory (completely) or on
disk instead, other than for technical reasons, like performance etc.
I am not an X-Hive expert though. I recommend asking them more details
themselves. I have looked, but didn't find a mailinglist, so you will
have to use the support mailaddress you can find at
http://support.x-hive.com/user/index.html.
I have met these people myself and have colleagues that have used this
database in combination with XSL technology. We were impressed by it.
Why not download a free trial and experiment a bit?
;-)
I looked there and:
http://support.x-hive.com/kb/index.html
which does talk about XSL, but it does not look like they use
an optimized DOM in the examples.
Drs. G.P.H. Josten
Consultant
Daidalos BV
Source of Innovation
Hoekeindsehof 1-4
2665 JZ Bleiswijk
Tel.: +31 (0) 10 850 1200
Fax: +31 (0) 10 850 1199
www.daidalos.nl
KvK 27164984
De informatie - verzonden in of met dit emailbericht - is afkomstig van
Daidalos BV en is uitsluitend bestemd voor de geadresseerde. Indien u dit
bericht onbedoeld hebt ontvangen, verzoeken wij u het te verwijderen. Aan dit
bericht kunnen geen rechten worden ontleend.
--~------------------------------------------------------------------
XSL-List info and archive: http://www.mulberrytech.com/xsl/xsl-list
To unsubscribe, go to: http://lists.mulberrytech.com/xsl-list/
or e-mail: <mailto:xsl-list-unsubscribe(_at_)lists(_dot_)mulberrytech(_dot_)com>
--~--