RE: My XSLT project is getting larger, maybe too large

why not use XINDICE with the webdav plugin ? you can manipulate your xml as if they were seperate documents but gain the performance benefits; is it just simple XPATH queries to generate stats, if so you can use the xpath query engine built in,
lastly, if you still want to use msxml, you can access every xml document using a typical HTTP GET request.

I find it works well, though the XINDICE project seems to be atrophying just a bit at apache at http://xml.apache.org/xindice/


gl, jim fuller

-----Original Message-----
From: John Reid [mailto:John.Reid@xxxxxxxxxxxxxxx]
Sent: 18 September 2003 08:07
To: xsl-list@xxxxxxxxxxxxxxxxxxxxxx
Subject:  My XSLT project is getting larger, maybe too large


My project started of with a text XML database for one unit of people
(about 80). It uses MSXML to generate HTML from a transformation. It
stands a good chance of growing to 20 units and maybe 100 units. Each
unit could have their own text XML database. But I can see where
somebody is going to want stats across them all. So I am asking for
advice. While I would guess that the app could be migrated to say
Tamino, the current database standard used is SQL Server. Could I
continue with mutiple XML text files, I kinda like them for they are
fast and easy to manipulate (ie if there is corruption then they can
simply be edited - with care!) any hints, guidelines suggestions would
help.

Salud

John Reid


 XSL-List info and archive:  http://www.mulberrytech.com/xsl/xsl-list


 XSL-List info and archive:  http://www.mulberrytech.com/xsl/xsl-list