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


Help: OASIS Mailing Lists Help | MarkMail Help

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: XML Integration

Switching to XML is usually a process that eventually replaces other types
of client-to-server communications. Main question is to decide if you want
to use servlets or RPCs.
In our cases we made choice in favor of servlets/JSP/ASP as a gradual
architectural transition path.
However, you should be aware that in
browser-based applications through the lifespan of the project we had to use
3 interfaces - http form request in the beginning, XML in hidden form field
for navigation as intermediate step and pure XML requests in flexible JSP or
ASP frameworks. As a result, we end up using "helper" class that provides us
with with data access to submitted information but hides the fact of the way
information was "transported" and parsed by server. Any parser should
provide enought
flexibility for simple protocols - we used MSXML and Xerces/Xalan in our
For pure HttpRequests IE offers HttpRequest object. Netscape has couple of
XML plug-ins
that have identical API - your code should be quite close for both browsers.
Anatole Tartakovsky

----- Original Message -----
From: "Bill Cummings" <cummings@sae.org>
To: <Jcean@cisglobal.com>; <xml-dev@lists.xml.org>
Sent: Monday, January 29, 2001 12:27 PM
Subject: Re: XML Integration

Perhaps XML-RPC?    www.xmlrpc.com

>>> Jon Ceanfaglione <Jcean@cisglobal.com> 01/29 11:13 AM >>>

I'm getting ready to begin an integration project using HTTP to transmit and
receive XML formatted data.  What I'm interested in is getting some
suggestions about how you might go around transmittng and receiving the XML.
I have my own ideas, like doing a read on the entire HTTP stream and looking
for the beginning xml tag and the ending xml tag and then load it into a
DOM.  What are some other ideas out there?




The information contained in this communication is intended only for the use
of the recipient named above, and may be legally privileged, confidential
and exempt from disclosure under applicable law. If the reader of this
communication is not the intended recipient, you are hereby notified that
any dissemination, distribution, or copying of this communication, or any of
its contents, is strictly prohibited.  If you have received this
communication in error, please re-send this communication to the sender and
delete the original communication and any copy of it from your computer
system. Thank you.