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

RE: Transmitting XML between different applications

  • To: Michael Kay <mike@s...>, xml-dev@l...
  • Subject: RE: Transmitting XML between different applications
  • From: Mukul Gandhi <mukul_gandhi@y...>
  • Date: Sat, 19 Feb 2005 02:22:55 -0800 (PST)
  • Comment: DomainKeys? See http://antispam.yahoo.com/domainkeys
  • Domainkey-signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com; b=oyn/jPjvOcOpKsAfi2SsR0/vCdcjzvtEh6xyB/qX/Tu6k9MPGPs2v+YdP2ukgQ427fOMYDOwE7iXw9iopdwJZAm+xPonhdM5alCOTNKt8TAaUTbET1+knIbEaGIuuR9by4/fFC5nKPwx72G3otp8ed2BpuQltgThvOfnxA/3/jw= ;
  • In-reply-to: <E1D2RFP-0000YE-00@u...>

transmitting xml documents
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@s...> 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 
 


PURCHASE STYLUS STUDIO ONLINE TODAY!

Purchasing Stylus Studio from our online shop is Easy, Secure and Value Priced!

Buy Stylus Studio Now

Download The World's Best XML IDE!

Accelerate XML development with our award-winning XML IDE - Download a free trial today!

Don't miss another message! Subscribe to this list today.
Email
First Name
Last Name
Company
Subscribe in XML format
RSS 2.0
Atom 0.3
 

Stylus Studio has published XML-DEV in RSS and ATOM formats, enabling users to easily subcribe to the list from their preferred news reader application.


Stylus Studio Sponsored Links are added links designed to provide related and additional information to the visitors of this website. they were not included by the author in the initial post. To view the content without the Sponsor Links please click here.

Site Map | Privacy Policy | Terms of Use | Trademarks
Free Stylus Studio XML Training:
W3C Member
Stylus Studio® and DataDirect XQuery ™are products from DataDirect Technologies, is a registered trademark of Progress Software Corporation, in the U.S. and other countries. © 2004-2013 All Rights Reserved.