|
> -----Original Message----- > From: Nathan M. Andelin > > > From: "Bartell, Aaron L. (TC)" > > Addressing your other concerns over the amount of XML > > steps. I think this is becoming par for the course when you > > need to communicate a bunch of different ways and you don't > > always know what is going to be on the receiving end of your > > program. > > Isn't the final output HTML? Isn't the receiver a browser? That's just it. It's not necessarily a browser. It may be a cell phone or a PDA, or something else tomorrow. That the justification for not simply generating HTML. I don't want to send the same HTML to a device that has a screen 200 pixels wide (or whatever) as I send to a browser. NOTICE: This E-mail may contain confidential information. If you are not the addressee or the intended recipient please do not read this E-mail and please immediately delete this e-mail message and any attachments from your workstation or network mail system. If you are the addressee or the intended recipient and you save or print a copy of this E-mail, please place it in an appropriate file, depending on whether confidential information is contained in the message.
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.
midrange.com
