Return-Path: Delivered-To: new-httpd-archive@hyperreal.org Received: (qmail 22550 invoked by uid 6000); 2 Nov 1999 20:41:44 -0000 Received: (qmail 22520 invoked from network); 2 Nov 1999 20:41:41 -0000 Received: from ss04.nc.us.ibm.com (HELO 32.97.136.234) (32.97.136.234) by taz.hyperreal.org with SMTP; 2 Nov 1999 20:41:41 -0000 Received: from johngalt (unverified [9.37.75.6]) by johngalt.raleigh.ibm.com (EMWAC SMTPRS 0.83) with SMTP id ; Tue, 02 Nov 1999 15:47:19 -0500 Message-ID: <007f01bf2573$74396b10$064b2509@raleigh.ibm.com> From: "Bill Stoddard" To: Subject: Simple Object Access Protocol Date: Tue, 2 Nov 1999 15:47:18 -0500 Organization: IBM Corp. 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.00.2314.1300 X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2314.1300 Sender: new-httpd-owner@apache.org Precedence: bulk Reply-To: new-httpd@apache.org Is anyone on the list familier with SOAP? http://www.ietf.org/internet-drafts/draft-box-http-soap-00.txt SOAP is an HTTP/XML based RPC mechanism being pushed by MS, I think, as a replacement for DCOM. Does anyone see any inherent difficulties with accomodating SOAP in Apache? From reading the IETF draft, it appears we would need to support the M-Post method and recognise some additional headers. Doesn't sound to onorous. Beyond that, seems the capability to build and transport SOAP objects would rely on a good XML parser and a scripting engine (PHP, mod_perl, Jakarta, etc). What's SOAPs status in the IETF? The upcoming IETF in DC doesn't mention it or an HTTP WG meeting either. Bill