Lists Home |
Date Index |
Michael Kay 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
>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
>It seems a bit kludgey to me, but as a cheap and cheerful way of achieving
>asynchronous communication with minimal configuration overhead, it's
it's cheap and cheerful alright. but can be very effective. you have the
advantage of the email filtering process to protect you from a lot of
i've used it a lot where cheap and cheerful fits the bill. the biggest
problem is congestion with other email traffic so you can't guarantee
response times. if that's important then you need a more dedicated
product or a more sophistcated email setup.
i use sendmail for these little applications :) as it's pretty easy to
configure these days.
>The xml-dev list is sponsored by XML.org <http://www.xml.org>, an
>initiative of OASIS <http://www.oasis-open.org>
>The list archives are at http://lists.xml.org/archives/xml-dev/
>To subscribe or unsubscribe from this list use the subscription
tel;cell:+61 411 287 530