RE: [xml-dev] Transmitting XML between different applications

[Mukul Gandhi <mukul_gandhi@yahoo.com>]

Thank you Mr. Kay for valuable suggestions.. I just
have now few more doubts..

1) The binary XML idea. I would appreciate some
reference. How it fits into technical architecture,
vendor support etc?

2) One question I asked earlier in this thread. If I
create a DOM object at source application using
Xerces; can I consume this DOM object using another
parser at recieving end (for e.g. Oracle). My feeling
is no.. The reason being - A specific parser uses its
own data structures to implement DOM interfaces. So
another parser cannot read the DOM..

3) You said -"other possibilities include writing out
SAX events to a SAX serializer". How is it actually
implemented? My understanding is - SAX API is used
while reading the XML document. Can it also be used to
*create* XML documents?

Regards,
Mukul

--- Michael Kay <mike@saxonica.com> wrote:

> > Hello Mr. Kay,
> >   When you say, "probably not to encode it at all,
> > i.e. send the XML document as is", do you mean
> send
> > the XML document as a string?
> 
> Yes. An XML document is a string.
> > 
> > My sending application will create XML (for e.g.
> from
> > browser input). I think best way to create a XML
> > structure from discreet input values, would to use
> a
> > DOM parser, and then serializing the DOM object
> into
> > string? Is this the best way to create XML string
> at
> > source application!
> 
> That's one way. Alternatives to DOM, within the same
> architectural approach,
> include JDOM and XOM - both are much easier to use.
> Other possibilities
> include writing out SAX events to a SAX serializer,
> or writing angle-bracket
> syntax directly. Which is easiest depends on your
> application.
> > 
> > I recently came to know about 2 applications
> > exchanging XML via email as transport. The sending
> > application sends "XML file" attachments to a
> specific
> > email address. The receiving application extracts
> the
> > XML attachments from email. Is this a practical
> > approach?
> 
> It seems a bit kludgey to me, but as a cheap and
> cheerful way of achieving
> asynchronous communication with minimal
> configuration overhead, it's
> certainly viable.
> 
> Michael Kay
> http://www.saxonica.com/




		
__________________________________ 
Do you Yahoo!? 
Meet the all-new My Yahoo! - Try it today! 
http://my.yahoo.com