Return-Path: Mailing-List: contact axis-dev-help@xml.apache.org; run by ezmlm Delivered-To: mailing list axis-dev@xml.apache.org Received: (qmail 70574 invoked from network); 7 Feb 2001 18:34:47 -0000 Received: from cosrel2.hp.com (156.153.255.162) by h31.sny.collab.net with SMTP; 7 Feb 2001 18:34:47 -0000 Received: from omgw5.rsvl.itc.hp.com (omgw5.rsvl.itc.hp.com [15.34.240.65]) by cosrel2.hp.com (Postfix) with ESMTP id 3F720FB for ; Wed, 7 Feb 2001 11:34:36 -0700 (MST) Received: from xboibrg2.boi.hp.com (xboibrg2.boi.hp.com [15.56.8.172]) by omgw5.rsvl.itc.hp.com (8.9.3 (PHNE_18979)/8.9.3 SMKit6.0.6 OpenMail) with ESMTP id LAA13621 for ; Wed, 7 Feb 2001 11:34:46 -0700 (MST) Received: by xboibrg2.boi.hp.com with Internet Mail Service (5.5.2653.19) id <1NNW1HWB>; Wed, 7 Feb 2001 11:34:45 -0700 Message-ID: From: "MURRAY,BRYAN (HP-FtCollins,ex1)" To: "'axis-dev@xml.apache.org'" Subject: RE: SOAPAction Date: Wed, 7 Feb 2001 11:30:00 -0700 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2653.19) Content-Type: text/plain; charset="iso-8859-1" X-Spam-Rating: h31.sny.collab.net 1.6.2 0/1000/N If SOAP (or XP) is ever to be truely transport independent, routing information will need to be inside the SOAP headers. I accept that the Body should never need to be opened for this type of processing - one of the benefits of a streaming parser, it is possible to stop parsing when you have the information you want. I also accept that HTTP routing can be done using information available only to HTTP (ie. target URI, and SOAPAction or other HTTP headers), but this doesn't really constitute a SOAP processor because it is not processing SOAP. Bryan Murray -----Original Message----- From: James Snell [mailto:jmsnell@intesolv.com] Sent: Wednesday, February 07, 2001 10:09 AM To: 'axis-dev@xml.apache.org' Subject: RE: SOAPAction In order to process the contents of a message, the envelope must be opened. However, there is a variety of ways to process the receipt of a message with out opening it. i.e., routing, logging, queue, etc. You may have a intermediary service that does nothing but routing of the message in which case the envelope may never have to be opened (it may be that due to various security requirements, the intermediary may not even be allowed to open the envelope even if it wanted to). - James > -----Original Message----- > From: MURRAY,BRYAN (HP-FtCollins,ex1) [mailto:bryan_murray@hp.com] > Sent: Wednesday, February 07, 2001 10:01 AM > To: 'axis-dev@xml.apache.org' > Subject: RE: SOAPAction > > > In order to process a message, the envelope must be opened. Why is it > necessary to know the to which service a message is destined > before looking > at the message? > > Bryan Murray > > -----Original Message----- > From: James Snell [mailto:jmsnell@intesolv.com] > Sent: Wednesday, February 07, 2001 8:59 AM > To: 'axis-dev@xml.apache.org' > Subject: RE: SOAPAction > > > +1. > > I'd much prefer dispatching services based on some unique URI (email > address, url+query-string, etc). "Opening" the message > envelope simply to > find out which service to invoke is definitely NOT the way to go. > > - James >