Return-Path: Delivered-To: apmail-xml-axis-dev-archive@xml.apache.org Received: (qmail 51917 invoked by uid 500); 28 Oct 2001 19:16:37 -0000 Mailing-List: contact axis-dev-help@xml.apache.org; run by ezmlm Precedence: bulk Reply-To: axis-dev@xml.apache.org list-help: list-unsubscribe: list-post: Delivered-To: mailing list axis-dev@xml.apache.org Received: (qmail 51908 invoked from network); 28 Oct 2001 19:16:37 -0000 Message-ID: <00fc01c15fe4$bf754380$6b00a8c0@ne.mediaone.net> From: "Glen Daniels" To: References: <3.0.1.32.20011026154218.0159ad38@unrealities.com> <3.0.1.32.20011028104659.013931e8@unrealities.com> Subject: Re: Proposed change to Message API Date: Sun, 28 Oct 2001 14:14:20 -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 6.00.2600.0000 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000 X-Spam-Rating: 64.125.133.20 1.6.2 0/1000/N > Change "SOAP part" to "root part" and I'm sold. (Incidentally, Glen, is Axis > SOAP-specific or not, to your mind?) Here's my take : for v1.0, it is absolutely SOAP specific. I don't know about the rest of you, but I would really like to get a first complete version of Axis out the door by the end of the year. Now, this will really mean a "post-beta-release-candidate" type of thing, since we're using JAX API's which won't be released yet, but still there's a functionality line in the sand that I'd like to draw, and revamping to do generic non-SOAP protocols is something that seems clearly on the other side of that line to me. Let's do that later if there's a demand for it. --Glen