Re: [xsl] Large content rendering in XSLT

Subject: Re: [xsl] Large content rendering in XSLT
From: "Ric Johnson" <ricjohnsoniii@xxxxxxxxx>
Date: Mon, 19 May 2008 15:33:22 -0400
Remember,

For <relative> LARGE datasets, a steaming model (SAX) may be a better
approach than XSL or DOM

Ric Johnson

On Mon, May 19, 2008 at 2:12 PM, Geert Josten <geert.josten@xxxxxxxxxxx> wrote:
> Hi Senthil,
>
> Are you sure you mean K as in Kilobyte and not something of bigger size?
> 500k is in particularly big. A DOM tree for an XML document of about 500
> k would consume roughly about 5 Mb (some slight guessing here). Creating
> a duplicate of the data through XSLT, cached as a DOM before writing it,
> would consume double that size.
>
> My figures are perhaps a bit optimistic, but it should give a fair
> impression of the scale of things.
>
> Note: there are ways to efficiently process even documents of sizes 50
> Mb and bigger, by processing them inside XML databases with XSLT support
> and which are capable of providing access to those documents through
> persistent DOM objects.
>
> Kind regards,
> Geert
>
>>
>
>
> 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.
>
>
>> From: Senthilkumaravelan K [mailto:skumaravelan@xxxxxxxxxxxxxx]
>> Sent: maandag 19 mei 2008 19:29
>> To: xsl-list@xxxxxxxxxxxxxxxxxxxxxx
>> Subject: [xsl] Large content rendering in XSLT
>>
>> Hi Guys ,
>> I am looking for a solution, where I could include large
>> dynamic content about (500k) through XSLT?
>> is it any viable option to include it through this technology?
>>
>> We would like to add ,Refunding policy in different languages
>> through the DB source. Any suggestion are pointers are appreciated.
>>
>> Thanks,
>> Senthil

Current Thread