W3C home > Mailing lists > Public > www-ws-arch@w3.org > August 2002

Fw: [wsi_wsbasic] RE: Call-back scenario

From: Christopher B Ferris <chrisfer@us.ibm.com>
Date: Thu, 15 Aug 2002 15:16:29 -0400
To: www-ws-arch@w3.org
Message-ID: <OFAFD133AD.07415B72-ON85256C16.00693294-85256C16.0069CC92@rchland.ibm.com>
FYI, here was my response.

Christopher Ferris
Architect, Emerging e-business Industry Architecture
email: chrisfer@us.ibm.com
phone: +1 508 234 3624
----- Forwarded by Christopher B Ferris/Waltham/IBM on 08/15/2002 03:09 PM 
-----

Christopher B Ferris/Waltham/IBM@IBMUS wrote on 08/15/2002 02:13:17 PM:

> 
> Jorgen, 
> 
> I can comment on this. First off, the work you cite was actually 
developed 
> in the XMLP WG. WSAWG has adopted that work as a starting point for its 
own 
> work. The concept of SOAP handler was somewhat controversial within the 
> XMLP WG. Essentially, it was a generalization of a software handler for 
> what the SOAP1.2 spec now calls a feature (expressed as a SOAP header 
block). 
> It is something that most considered to be an *add on* to the standard 
> "infrastructure" (the SOAP processor). It could be a "pluggable" 
component 
> that is mapped to a particular (set of) SOAP header block(s) that the 
> SOAP processor invokes based on the mapping of QNames. Of course, that 
is not 
> to say that it couldn't be baked into the standard "infrastructure". 
> 
> The blue line distinguishes between what is in scope for the SOAP1.2 
> spec (the SOAP processor) and that which is not. Technically, it is 
> application space, but that doesn't mean that the processing cannot be 
> delegated to a standard middleware component. 
> 
> In any event, I think I concur with your conclusion. 
> 
> Cheers, 
> 
> Christopher Ferris
> Architect, Emerging e-business Industry Architecture
> email: chrisfer@us.ibm.com
> phone: +1 508 234 3624 
> 
> "Jorgen Thelin" <Jorgen.Thelin@capeclear.com> wrote on 08/15/2002 
01:37:09 PM:
> 
> > 
> > Can someone closely involved with the W3C Web Services Architecture
> > group comment on the intent in the scenario document quoted below on
> > exactly whether "SOAP Handlers" are intended to be 
application-specific
> > code rather then standard "infrastructure" code?
> > 
> > Certainly that is the way it looks to me from the diagram in section
> > S070 quoted below, but the associated W3C Glossary is somewhat vague 
on
> > this point.
> > 
> > http://www.w3.org/2002/ws/arch/2/06/wd-wsa-gloss-20020605.html
> > SOAP handler
> > An SOAP handler is responsible for processing SOAP Blocks targeted at 
it
> > according to any rules defined in the corresponding SOAP module.
> > 
> > 
<snip/>
Received on Thursday, 15 August 2002 15:17:27 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Tuesday, 3 July 2007 12:25:04 GMT