you mention routing - if you sent soap to a host for routing then it's not 1-to-1 and must be intermediated connection, correct ?
you mean most web services are very simple sample for demo only and commerical implementations are much more complex?
and you mention "application agent" are u mening Ultimate SOAP receiver?
you mention "intermediary" is meaning same as "handler with the hosting SOAP engine." correct?
Anne Thomas Manes <[EMAIL PROTECTED]> wrote:
People typically use a SOAP Header to perform system-level functionality, such as authentication, session management, and routing. These functional requirements apply to both 1-to-1 and intermediated connections.
Most web services on xmethods.com do not require these system-level functions.
Typically header information is not passed to the application agent. Instead, the header is processed either by an intermediary or by a handler with the hosting SOAP engine.
Anne
On 3/5/06, susae lee <[EMAIL PROTECTED]> wrote:i just read through Axis user doc, but all sample app it mention doesn't show how to use the <HEADER> tag inside soap request / response.1 -- is <HEADER> tag not much a use when doing 1 - 1 host to host request /response?2 -- <HEADER> is only useful when soap massage need to pass multiple endpoints / hosts ?3 -- Why most of the web services at www.xmethods.net don't use <HEADER> tag on request / response xml?4 -- Is that in most cases, BODY tag in soap is enough? no HEADER needed?5 -- Hosts in between web service client + provider process <HEADER> elements but not the content of BODY element? and the Ultimate SOAP receiver will process the BODY elements?
Yahoo! Mail
Bring photos to life! New PhotoMail makes sharing a breeze.
Yahoo! Mail
Bring photos to life! New PhotoMail makes sharing a breeze.
