Received: from bush.rutgersinsurance.com (rutgersinsurance.com
 [38.138.71.194])
	by mail.postgresql.org (8.11.1/8.11.1) with ESMTP id eAEK5fs57106
	for <pgsql-interfaces@postgresql.org>;
	Tue, 14 Nov 2000 15:05:41 -0500 (EST)
	(envelope-from aalang@rutgersinsurance.com)
Received: from 6014cwpza006 ([10.10.10.51])
	by bush.rutgersinsurance.com (8.9.3/8.9.3) with SMTP id PAA29576
	for <pgsql-interfaces@postgresql.org>; Tue, 14 Nov 2000 15:08:23 -0500
Message-ID: <028201c04e76$68f3f5e0$330a0a0a@6014cwpza006>
From: "Adam Lang" <aalang@rutgersinsurance.com>
To: "pgsql-interfaces" <pgsql-interfaces@postgresql.org>
References: <006901c04e43$25f718e0$330a0a0a@6014cwpza006>
	<3A119482.3B48D7A8@home.com>
Subject: Re: OT: Heterogenous networks
Date: Tue, 14 Nov 2000 15:06:09 -0500
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 5.50.4133.2400
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400
X-Archive-Number: 200011/151
X-Sequence-Number: 187

I agree, it is different, but XML and SOAP means no licensing, not platform
dependent and standardized. :)

I do appreciate the info and feedback offered.

Adam Lang
Systems Engineer
Rutgers Casualty Insurance Company
----- Original Message -----
From: "Red Pineseed" <yue207@home.com>
To: "pgsql-interfaces" <pgsql-interfaces@postgresql.org>
Sent: Tuesday, November 14, 2000 2:37 PM
Subject: Re: [INTERFACES] OT: Heterogenous networks


> SOAP is based on XML-RPC while it corrected some of the
> XML-RPC limitations. Both SOAP and XML-RPC use HTTP
> protocols to exchanges XML packets through procedure calls,
> which is different form CORBA and RMI.
>
>
> Philip
>
>
>
> Adam Lang wrote:
> >
> > Sorry for the off topic post, but this is just to finish up a comment
about
> > XML I made earlier.
> >
> > Biztalk is the MS implementation, but SOAP is the protocol that wraps
XML
> > around the data.  Here is a quote:
> >
> > Abstract
> > SOAP is a lightweight protocol for exchange of information in a
> > decentralized, distributed environment. It is an XML based protocol that
> > consists of three parts: an envelope that defines a framework for
describing
> > what is in a message and how to process it, a set of encoding rules for
> > expressing instances of application-defined datatypes, and a convention
for
> > representing remote procedure calls and responses. SOAP can potentially
be
> > used in combination with a variety of other protocols; however, the only
> > bindings defined in this document describe how to use SOAP in
combination
> > with HTTP and HTTP Extension Framework.
> >
> > http://www.w3.org/TR/SOAP/
> >
> > It is not an MS technology.
> >
> > But in regards to someone else's comment earlier, makes the idea of
> > postgresql support for XML interesting.
> >
> > Adam Lang
> > Systems Engineer
> > Rutgers Casualty Insurance Company