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

FW: [wsi_wsbasic] RE: Call-back scenario

From: Ugo Corda <UCorda@SeeBeyond.com>
Date: Thu, 15 Aug 2002 10:43:39 -0700
Message-ID: <C513FB68F8200244B570543EF3FC653708AE362A@MAIL1.stc.com>
To: www-ws-arch@w3.org

FYI. Here is a question raised within the WS-I Basic Profile and directed to
the WSAWG.

Ugo

-----Original Message-----
From: Jorgen Thelin [mailto:Jorgen.Thelin@capeclear.com]
Sent: Thursday, August 15, 2002 10:37 AM
To: WS-I WS Basic Profile Mailing List
Subject: [wsi_wsbasic] RE: Call-back scenario



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.


I may be in danger of labouring the point here, but to me this all
points to the Basic Profile largely concentrating on the "SOAP
Processor" blocks in the W3C diagrams - i.e. the bits below the blue
line on the diagrams.  I realise this is possible a gross
over-simplification, but this again points me to the conclusion that the
handling of correlation headers is in the "application" layer, not the
"Basic Profile" layer.



> -----Original Message-----
> From: Steve Jenisch [mailto:Steve.Jenisch@sas.com] 
> Sent: 15 August 2002 18:04
> To: WS-I WS Basic Profile Mailing List
> Subject: [wsi_wsbasic] RE: Call-back scenario
> 
> 
> If the w3c async architecture usage scenario - 
> http://www.w3.org/TR/2002/WD-ws-arch-scenarios-20020730/#S070 
> - meets our needs, why don't we just adopt it and move on?
> 
> 
> Steve
> 
Received on Thursday, 15 August 2002 13:44:20 GMT

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