RE: [i95, i22] - Proposal for clarifying use of SOAPAction

Dick --

I think I addressed much of your note in my last post, with the exception of
this --

> I agree, however that's not possible without changing the 
> SOAP spec to allow
> implementers to specify their own Content-types. All SOAP 
> messages carried
> via
> HTTP are Content-type: text/xml according to section 6 of the 
> SOAP spec,
> which
> states:
> 
> "HTTP applications MUST use the media type "text/xml" according to RFC
> 2376 [3] when including SOAP entity bodies in HTTP messages."

I think my take on this is pretty straightforward -- the spec should change
to reflect a more appropriate MIME type for XMLP (or SOAP), vis a vis
application/xmlp+xml or application/protocol+xml.   I believe that would
eliminate the SOAPAction header requirement and build a better stack.

Regards --

jeffrey kay <jkay@engenia.com>
chief technology officer, engenia software, inc. 
"first get your facts, then you can distort them at your leisure" -- mark
twain 
"golf is an endless series of tragedies obscured by the occasional miracle"
-- sports illustrated 
"if A equals success, then the formula is A equals X plus Y plus Z. X is
work. Y is play. Z is keep your mouth shut." -- albert einstein