W3C home > Mailing lists > Public > xml-dist-app@w3.org > April 2001

RE: [AM] - Modules and Handlers

From: Mark Jones <jones@research.att.com>
Date: Thu, 12 Apr 2001 16:40:33 -0400 (EDT)
Message-Id: <200104122040.QAA14189@glad.research.att.com>
To: jones@research.att.com, rhinewu@hotmail.com, wsadiq@vitria.com, xml-dist-app@w3.org
	> From: Waqar Sadiq <wsadiq@vitria.com>
	> To: "'Mark Jones'" <jones@research.att.com>, rhinewu@hotmail.com,
	>         xml-dist-app@w3.org
	> Subject: RE: [AM] - Modules and Handlers
	> Date: Thu, 12 Apr 2001 11:50:44 -0700

	> As I understand, XMLPApplication is the glue which associates one or more
	> XMLP handlers together to form a specific configuration (maintaining any
	> ordering between the handlers and so forth) .  XMLP module, on the other
	> associates the XMLPApplications to the XMLPBlocks that those handlers can
	> process.  These are naturally logical abstractions and do not indicate a
	> physical structure.

If you look at section 2 of the SOAP spec, it talks of the SOAP
application receiving a SOAP message, the SOAP application being the
ultimate destination of the message, the SOAP application forwarding
the message, etc.  That is the sense in which the SOAP application
is the behavioral part of the SOAP processor.  Indeed, it is also the
glue that controls how the handlers for modules get applied.


	Waqar Sadiq
	Vitria Technologies
	13727 Noel Road
	Tower 2, Suite 600
	Dallas, TX 75240
	Phone:   (469) 385-3046
	Fax:       (972) 739-2465
Received on Thursday, 12 April 2001 16:40:50 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 22:01:12 UTC