Lists Home |
Date Index |
- To: Michael Kay <firstname.lastname@example.org>, email@example.com
- Subject: RE: [xml-dev] Transmitting XML between different applications
- From: Mukul Gandhi <firstname.lastname@example.org>
- Date: Sat, 19 Feb 2005 01:38:36 -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=GRcqmWaBCsUT8QPKwMDJ7ZlwEtzG0Wj2I8Hk+KFevP2l19wCN+1jLQUB2V6G8A/zNgh30AU5MWWGrhIEg1KLmuJWcqqd5i3LwHaXFp2bnNf4aAQvWLeEm8BL4JRKL+L94YqyFYNz/MshSHqSpdxu+oyRX1mzIXu7Acn4M8l5HBw= ;
- In-reply-to: <E1D2QWt-0000Gbemail@example.com>
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?
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
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
I am curious to know about "binary XML" approach.. Can
you please provide some reading reference? Is binary
XML approach being used today in production systems,
or is it a research topic today?
--- Michael Kay <firstname.lastname@example.org> wrote:
> I mean that the best practical way of encoding an
> XML document as a stream
> of bytes for transmission over the wire is probably
> not to encode it at all,
> i.e. send the XML document as is.
> (Of course there may be better ways in particular
> cases, see the binary XML
> permathread; but a Java serialization of a DOM is
> unlikely to be such a
> Michael Kay
Do you Yahoo!?
Yahoo! Mail - 250MB free storage. Do more. Manage less.