Not sure if this is a Pro or Con, but you /should/ have a server-side
process insert the PI so you are not hardcoding your presentation to the
content.
Another Con is that you can't chain transformations.
On Tue, 20 Feb 2007 08:42:00 -0500, Robert Koberg <rob(_at_)koberg(_dot_)com>
wrote:
On Tue, 20 Feb 2007 08:25:15 -0500, Abel Braaksma
<abel(_dot_)online(_at_)xs4all(_dot_)nl> wrote:
Perhaps it is worthwhile to create a little list with pros and cons for
people that are new to the subject so that anyone can decide for
his/her own situation. I understand that you know pretty much of this
type of transformation invocation, maybe you can help improving a Wiki
article on this subject (not yet there).
Not complete, I'm sure, but...
Cons:
- no caching of the processor object
- when using XHR (XMLHttpRequest), the transform will not be invoked.
You will have to parse the DOM to find the PI and apply the transform
from JS.
Pros:
- simple
- works in almost every browser (just not in XHR)
best,
-Rob
--~------------------------------------------------------------------
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>
--~--
--
Using Opera's revolutionary e-mail client: http://www.opera.com/mail/
--~------------------------------------------------------------------
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>
--~--