Jim,
Yes I know they are optional, but as when you are in a mall, you want what you
see and maybe it was not what you first come for, so if it's there you start
using it. Then you find out that your application is no longer standard and
wow, how to come back.
I'll check the exslt.org for the protability issue.
I cannot afford buying such a book. They are in u$s down here and I cannot eat
it after reading.
No. I don't think XSLT is bounded on the browser, but somehow, if you don't
have MSXML in the IE in your machine, XSLT would not be processed (at least,
this is what I understood from previous msgs, and which you also point out in
your last answer: "wherever XSLT processing takes place, be it in the client or
server, will require an xslt processor to be installed".
Regards, Claudio.
-----Original Message-----
From: Jim Fuller [mailto:jim(_dot_)fuller(_at_)stuartlawrence(_dot_)com]
Sent: Miércoles, 02 de Julio de 2003 11:07 a.m.
To: xsl-list(_at_)lists(_dot_)mulberrytech(_dot_)com
Subject: RE: [xsl] xsl:sort in old MSXML
Sorry, I don't think I've confused. I understand Saxon is an
XSLT processor implementation, as well as MSXML. But going
this path seems (as I said, from the msgs I read in this
forum) that incorportes also other features that are not
those features are optional to use, take a look at www.exslt.org when using
such extension functions and addressing concerns of portability across
different XSLT processors
available in other processors though going to get errors when
processing under different environments (for instance, the
clients that do not have MSXML installed on their machine
will not be able to see the trasnformation, and I guess the
same occurs with Saxon).
well use u could design an app that takes advantage of client side processing,
or just have everything server side.
Probably all the confusion stands in that I still don't get
the architecture of the whole paradigm.
XML ---> XSLT ---> HTML/PDF/WAP/etc.
(1) (2) (3)
thats why i said to just start using it, go through examples, buy a book, goto
www.dpawson.co.uk and learn some of the fundamentals.
(1) could be in server side, client side or both?
yes to both
(2) could be in server side, client side or both?
Where does (2) takes place? in server side, client side or both?
these types of questions really are not about architecture, but 'where' xslt
processing takes place, which could be in both the client or server...its up to
you to decide where.
If (2) takes place in server side, do I need to have
Saxon/MSXML/"other processor" in the server?
well, yes.....I think that u may be thinking that xslt is somehow bounded to
html browsers....they are not, it just so happens that xslt is supported in IE
and Mozilla, which is great.
If (2) takes place in client side, does the client machine
need to have Saxon/MSXML/"other processor" installed on it?
wherever XSLT processing takes place, be it in the client or server, will
require an xslt processor to be installed.
cheers, jim
This e-mail and any files transmitted with it are confidential and intended
solely for the use of the individual or entity to whom they are addressed. If
you are not the intended recipient please contact the sender immediately. Any
disclosure, copying, distribution or any other use of this communication is
strictly prohibitedand may be unlawful. Stuart Lawrence Marketing
Communications Limited reserves the right to monitor and intercept
communications for unlawful business purposes.
This also confirms that this message has been swept for viruses, although
Stuart Lawrence Marketing Communications Limited accepts no responsibility for
any loss or damage resulting directly or indirectly from the use of this email
or contents.
XSL-List info and archive: http://www.mulberrytech.com/xsl/xsl-list
XSL-List info and archive: http://www.mulberrytech.com/xsl/xsl-list