Component Markup Language
shecter at darmstadt.gmd.de
Thu Feb 4 16:56:09 GMT 1999
Nigel Hutchison wrote:
> Then a server could project its own GUI api and leave it to the client side
> to choose C++, Java etc to build the interface at run time.
> I suspect that
> in most cases the bandwidth required to shift the XML GUI description would
> be quite a bit less than the
> compiled java classes. If this is so than "Even Cooler" would be XML GUI
> interpreter built into a Internet Browser.
How about this: Have one XSL document per client side scripting language. That is, different
XSL documents could implement:
Component-XML->DHTML (This particular one would give you your "Even Cooler" idea.)
...then, a client side browser applies whatever XSL template is best for it, gets the the
resulting kind of script it understands, and on the fly generates a UI.
xml-dev: A list for W3C XML Developers. To post, mailto:xml-dev at ic.ac.uk
Archived as: http://www.lists.ic.ac.uk/hypermail/xml-dev/ and on CD-ROM/ISBN 981-02-3594-1
To (un)subscribe, mailto:majordomo at ic.ac.uk the following message;
To subscribe to the digests, mailto:majordomo at ic.ac.uk the following message;
List coordinator, Henry Rzepa (mailto:rzepa at ic.ac.uk)
More information about the Xml-dev