Re: SOAP/1.1 issues list available

*  use of port 80 by default

I agree that the use of port 80 by default is not good.  But I would add
that the specification of any port at all belongs in a protocol-specific
spec.  If you extended Napster to do RPCs with SOAP, then the port choice 
might need to be the Napster port.  Which port to use is transport
dependent.

Whether HTTP SOAP should use port 80 or not is a different question.  I
suggest that any specific port number be replaced with either "the
default port of the substrate protocol" or "NOT the default port of the
substrate protocol".  It may be useful to have a matrix of protocol/port
details that say for protocol X use port Y.

- Lucas Gonze


 On Sat, 5 Aug 2000, Henrik Frystyk Nielsen wrote:
> In order to ensure that we don't drop anything on the floor regarding the
> SOAP/1.1 spec, C.J Williams and I have made an attempt of collecting the
> set of issues that have been brought up on the <soap@discuss.develop.com>
> and the <xml-dist-app@w3.org> list at:
> 
>     http://msdn.microsoft.com/xml/general/soapspec_issues.asp
> 
> linked from
> 
>     http://msdn.microsoft.com/xml/general/soaptemplate.asp
> 
> If there are obvious things that we have left out then please send mail to
> me <frystyk@microsoft.com> and C.J. <t-cjwill@microsoft.com> and cc the
> <soap@discuss.develop.com> and the <xml-dist-app@w3.org> as I don't know
> the overlap between the lists (otherwise sorry for the cross-posting).
> 
> Even though some of the issues have been though extensive debate on the
> mailing list (linked of the list above), we have not marked any as
> "closed" as we felt this would be inappropriate before some form of "last
> call" on the list. In the near future, we will send out such calls in
> order to close items.
> 
> Henrik Frystyk Nielsen
> mailto:frystyk@microsoft.com
> 
>

Received on Saturday, 5 August 2000 16:31:05 UTC