On Mar 9, 2004, at 5:01 PM, Colin Chalmers wrote:


Hi all,

Is anyone actually using DVSL for presentaion layer instead of say XSLT? Any performance issues to be concerned about?

I use it all the time. That said, it's not for on-line rendering, but static rendering.


There is supposedly a memory leak in DVSL - or there was so claimed a number of years ago when maven was generating large outputs with it - but there never was a fixable example. DVSL was involved during the execution when the OOM happened, but other things were as well.

We just implemented a solution based on XSLT and I have to say performace sucks!! Wasn't my choice of solution!

I'd be interested to see a timing comparison.


geir


/c


Geir Magnusson Jr wrote:


On Mar 4, 2004, at 8:28 PM, Tim Colson wrote:


Geir said

You would be much better served by using DVSL.

DVSL is good mojo. I dig it. :-)


But hey, when is DVSL going to make it out dev-limbo and into the core
(or somewhere).


I'd like to do a release soon. No reason not to. Won't get into vel core as it's something that uses velocity, not is velocity.


And what's the big diff between Anakia and DVSL?


Anakia
------
WHAT IS IT GOOD FOR: XML transformed to anything?
PRO:Cool name
PRO/CON:Older so maybe more mature, but also cruftier?


Anakia is a fully procedural style rendering system where you have to know the full document format ahead of time. It was an early part of velocity, created originally by Jon Stevens, and is used throughout the ASF.


It my opinion (and Jon's back when I cooked up DVSL), it should be retired in favor of DVSL.


DVSL
-------
WHAT IS IT GOOD FOR: XML transformed to anything
PRO:Funky acronym name - not as cool
PRO:way cooler than XSL
CON:in "DEV" which means "stay away" for many folks.


DVSL is a 'declarative' rendering system like XSL. It differs from XSL in that

a) you can break out into nice procedural code (the Velocity) at any time for your output render
b) you can stuff the context with objects to access data from other sources


An improvement to DVSL would be to, for pure XML work, generate SAX events (and ilk) to play better in layered transformation pipelines. Maybe once we get 1.0 out the door it will get more attention and someone will scratch that itch. So far, it hasn't been an itch for me.

geir




--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]


--
Geir Magnusson Jr                                   203-247-1713(m)
[EMAIL PROTECTED]


--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]



Reply via email to