[XML-DEV Mailing List Archive Home] [By Thread] [By Date] [Recent Entries] [Reply To This Message]

Re: Fast text output from SAX?

• To: Elliotte Rusty Harold <elharo@m...>
• Subject: Re: Fast text output from SAX?
• From: "Stephen D. Williams" <sdw@l...>
• Date: Thu, 15 Apr 2004 14:25:05 -0400
• Cc: "Hunsberger, Peter" <Peter.Hunsberger@S...>,XML DEV <xml-dev@l...>
• In-reply-to: <p06010203bca46bfb4c07@[192.168.254.88]>
• References: <1E0CC447E59C974CA5C7160D2A2854EC097DEA@S...> <p06010203bca46bfb4c07@[192.168.254.88]>
• User-agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.6b) Gecko/20031208

Elliotte Rusty Harold wrote:

> ...
>
> So I guess what I'm saying is you're right. There's no difference 
> between sending a serialized XML DOM across RMI and shipping some 
> other "binary" XML format. they're both incredibly fragile things that 
> will break and probably sooner rather than later.

You know, like Jpeg, Tiff/Group4, Word documents (!), PowerPoint, zip 
files, tar/cpio, jar files, gziped HTML, etc.

When you get a corrupted XML document, you can always magically recover 
just the right missing tags and information?  Wow, where is that method 
in the spec?

We're realistically talking about bugs or deficiencies in code, 
configuration, mismatch between applications, etc., not 'fragile things 
that break' from any perspective but schema co-evolution, configuration 
management, and programmer error, isn't that right?

You can add forward error correction, b64 or quoted text encoding, and 
other methods to prevent corruption, but the only cure for 
user/programmer/operator error is early error detection and clear 
warning.  When these have already been taken care of, through earlier 
testing in once sense or another, or other methods, it is not an issue.

sdw

-- 
swilliams@h... http://www.hpti.com Pers: sdw@l... http://sdw.st
Stephen D. Williams 703-724-0118W 703-995-0407Fax 20147-4622 AIM: sdw

• Follow-Ups:
  • Re: Fast text output from SAX?
    • From: Elliotte Rusty Harold <elharo@m...>

• References:
  • RE: Fast text output from SAX?
    • From: "Hunsberger, Peter" <Peter.Hunsberger@S...>
  • RE: Fast text output from SAX?
    • From: Elliotte Rusty Harold <elharo@m...>

• Prev by Date: XUL Compact Syntax Study Now Online - Is XML too hard for Aunt Trudie?
• Next by Date: Re: xml editors
• Previous by thread: RE: Fast text output from SAX?
• Next by thread: Re: Fast text output from SAX?
• Index(es):
  • Date
  • Thread