Subject: Re: XML/XSL on the client for dynamic UI From: "G. Ken Holman" <gkholman@xxxxxxxxxxxxxxxxxxxx> Date: Wed, 27 Oct 1999 07:56:26 -0400 |
But that misses the point: Transformations should *absolutely* take place on the client side for several reasons:
- from an idealist's standpoint, having the pre-transformation xml on the client side maintains the semantics of the original data, and in the case of a lossy tranformation maintains the data itself as well.
- from a pragmatist's standpoint, there's no reason those valuable processing cycles shouldn't be split up between the clients requesting the data, because a server's job is to serve data as fast as it can.
The flow of control Sean proposes for dealing with things given current technology is fine (I can't think of a better way of dealing with things), but misses these two pretty key points...
-- G. Ken Holman mailto:gkholman@xxxxxxxxxxxxxxxxxxxx Crane Softwrights Ltd. http://www.CraneSoftwrights.com/s/ Box 266, Kars, Ontario CANADA K0A-2E0 +1(613)489-0999 (Fax:-0995) Web site: XSL/XML/DSSSL/SGML services, training, libraries, products. Practical Transformation Using XSLT and XPath ISBN 1-894049-02-0 Next instructor-led training: 1999-11-08, 1999-11-09, 1999-12-05/06, - 1999-12-07, 2000-02-27/28, 2000-05-11/12, 2000-05-15
Current Thread |
---|
|
<- Previous | Index | Next -> |
---|---|---|
Re: XML/XSL on the client for dynam, disco | Thread | Re: XML/XSL on the client for dynam, disco |
Re: XML/XSL on the client for dynam, oberthier | Date | RE: Using xt with IIS and ASP, Siegfried Haag |
Month |