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

Re: SAX for Binary Encodings (SAD-SAX)

• To: <xml-dev@l...>
• Subject: Re: SAX for Binary Encodings (SAD-SAX)
• From: "Karl Waclawek" <karl@w...>
• Date: Sat, 8 Nov 2003 13:05:40 -0500
• References: <000f01c3a614$7a3e3600$650aa8c0@BOBDEV> <p06002002bbd2da85adc7@[192.168.254.4]>

> At 11:22 AM -0500 11/8/03, Bob Wyman wrote:
> 
> 
> >     public interface TypedContentHandler extends ContentHandler {
> >       public void values(java.lang.Object value)
> >          throws SAXException;
> >     }
> 
> 
> This won't work. There are numerous problems including:
> 
> 1. People want primitive data types often instead of objects.
> 2. It's type unsafe. OBject is not suitable replacement for 
> Date/Integer/int/etc.
> 3. What do you pass when the data doesn't match the schema?

Now, whether this should be called SAX or something else
is another question, but a better way to pass arbitrary
data would be to take advantage of existing knowledge
about marshalling/unmarshalling data across networks.

In short, in the content handler call-back, pass an UnMarshall
object, and when writing the data use a Marshall object.
In the case above, the Unmarshall object would then have
appropriate methods to indicate the basic data type
(like integer, boolean, string, ...) and a platform dependent
way of unmarshalling them. Sort of like RPC. One could
use the one of the existing ways of representing data
on the network for the binary encoding. 

Karl

• References:
  • RE: SAX for Binary Encodings (SAD-SAX)
    • From: "Bob Wyman" <bob@w...>
  • RE: SAX for Binary Encodings (SAD-SAX)
    • From: Elliotte Rusty Harold <elharo@m...>

• Prev by Date: Re: SAX for Binary Encodings (SAD-SAX)
• Next by Date: RE: SAX for Binary Encodings (SAD-SAX)
• Previous by thread: RE: SAX for Binary Encodings (SAD-SAX)
• Next by thread: Re: SAX for Binary Encodings (SAD-SAX)
• Index(es):
  • Date
  • Thread