OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.

 


Help: OASIS Mailing Lists Help | MarkMail Help

 


 

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

[ Lists Home | Date Index | Thread Index ]
  • To: Michael Kay <mike@saxonica.com>, xml-dev@lists.xml.org
  • Subject: RE: [xml-dev] Transmitting XML between different applications
  • From: Mukul Gandhi <mukul_gandhi@yahoo.com>
  • Date: Fri, 18 Feb 2005 20:05:42 -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=dQmVr/hHv6PJLhNX6zwVnuIIhrPvvtKApyuDNjQdUSi0IRwCY/dURq8sLdtvGxP5VPqKEEgV4/RfLMgnTPtX/lj79g4c9rj5vG0IRlIaERCTRzOp0m3SCz+7V3yrrvooHAh9dhz8eeL6Uxzq2S0ULgDsBTovcsTgrP48J8mLMXc= ;
  • In-reply-to: <E1D2H0D-0006Kc-00@ukmail1.eechost.net>

Hello Mr. Kay,
When you say "the best serialization format for XML
documents is... XML" , what do you mean? I understand,
that serialization means - encoding of objects into a
stream of bytes which can be transmitted over the
wire. Serialization is essentialy used for lightweight
persistence and for communication via sockets or RMI.

When we will transmit String or Java DOM object, they
will be serialized automatically..

Regards,
Mukul

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

> > I have a requirement to pass XML between 2
> different
> > applications. The 2 applications are running on
> > different machines, and are Java based. The sender
> > application will generate XML to be sent, and
> would
> > send the XML to the receiving application.
> 
> If the two applications are on different machines,
> then the document needs
> to be serialized to be sent from one to the other.
> For nearly all practical
> purposes, the best serialization format for XML
> documents is... XML. 
> > 
> > I want to know the possible approaches for this.
> > 
> > The following two approaches are coming to my
> mind.
> > 1) Create a DOM object at the sending application,
> and
> > send this DOM object to the recieving application.
> I
> > have some doubt with this approach.. 
> 
> The Java serialization of a DOM is going to be
> vastly less efficient than
> the XML representation.
> 
> > 
> > 2) Encode XML as string at the sending
> application,
> > and send this XML string to the receiving
> appliction.
> 
> Far better.
> > 
> > I want to compare the above approaches from
> > feasibility and performance point of view. I also
> want
> > to know other approaches..
> > 
> > As a secondary requirement, I want to make the XML
> > transmission reliable(i.e. guranteed and 1 time
> > delivery). I belive, I can use messaging softwares
> for
> > this (like WebSphere MQ and others). What are the
> best
> > practices for reliable transmission? Should I pass
> DOM
> > object, String.. etc.?
> 
> That's a requirement on the transport layer, which
> is quite independent of
> the message syntax chosen.
> 
> Michael Kay
> http://www.saxonica.com/


		
__________________________________ 
Do you Yahoo!? 
Yahoo! Mail - 250MB free storage. Do more. Manage less. 
http://info.mail.yahoo.com/mail_250




 

News | XML in Industry | Calendar | XML Registry
Marketplace | Resources | MyXML.org | Sponsors | Privacy Statement

Copyright 2001 XML.org. This site is hosted by OASIS