W3C home > Mailing lists > Public > xml-dist-app@w3.org > February 2002

Re: FYI: BCP 56, RFC 3205 on HTTP Layering

From: S. Alexander Jacobson <alex@shop.com>
Date: Thu, 14 Feb 2002 12:33:41 -0500 (EST)
To: Mark Nottingham <mnot@mnot.net>
cc: Larry Masinter <LMM@acm.org>, <xml-dist-app@w3.org>
Message-ID: <Pine.WNT.4.43.0202141228420.368-100000@gandolph.ASGARD.jms>
It is not so clear.  SOAP seems to diverge from
use of MIME unnecessarily.

The use of XML for
data packaging means that you can't easily use
existing web browsers to interact with web
services.
In contrast, browsers know how to send
multipart/form-data, and most web servers already
know how to process it.

XML also creates a blizzard of new rules that
implementers must contend with.  MIME is already
well understood and built into most server
libraries.

-Alex-

On Wed, 13 Feb 2002, Mark Nottingham wrote:

>
> Thanks for that, Larry; I hadn't seen it.
>
> It looks like SOAP/1.2 is on a path to conforming nicely.
>
> Cheers,
>
>
>
> On Wed, Feb 13, 2002 at 04:19:09PM -0800, Larry Masinter wrote:
> > -----Original Message-----
> > From: RFC Editor [mailto:rfc-ed@ISI.EDU]
> > Sent: Tuesday, February 12, 2002 4:27 PM
> > To: IETF-Announce:
> > Cc: rfc-ed@ISI.EDU
> > Subject: BCP 56, RFC 3205 on HTTP Layering
> >
> >
> >
> > A new Request for Comments is now available in online RFC libraries.
> >
> >
> >         BCP 56
> >         RFC 3205
> >
> >         Title:	    On the use of HTTP as a Substrate
> >         Author(s):  K. Moore
> >         Status:     Best Current Practice
> > 	Date:       February 2002
> >         Mailbox:    moore@cs.utk.edu
> >         Pages:      14
> >         Characters: 34785
> >         Updates/Obsoletes/SeeAlso:  None
> >
> >         I-D Tag:    draft-moore-using-http-01.txt
> >
> >         URL:        ftp://ftp.rfc-editor.org/in-notes/rfc3205.txt
> >
> >
> > Recently there has been widespread interest in using Hypertext
> > Transfer Protocol (HTTP) as a substrate for other applications-level
> > protocols.  This document recommends technical particulars of such
> > use, including use of default ports, URL schemes, and HTTP security
> > mechanisms.
> >
> > This document specifies an Internet Best Current Practices for the
> > Internet Community, and requests discussion and suggestions for
> > improvements.  Distribution of this memo is unlimited.
> >
> > This announcement is sent to the IETF list and the RFC-DIST list.
> > Requests to be added to or deleted from the IETF distribution list
> > should be sent to IETF-REQUEST@IETF.ORG.  Requests to be
> > added to or deleted from the RFC-DIST distribution list should
> > be sent to RFC-DIST-REQUEST@RFC-EDITOR.ORG.
> >
> > Details on obtaining RFCs via FTP or EMAIL may be obtained by sending
> > an EMAIL message to rfc-info@RFC-EDITOR.ORG with the message body
> > help: ways_to_get_rfcs.  For example:
> >
> >         To: rfc-info@RFC-EDITOR.ORG
> >         Subject: getting rfcs
> >
> >         help: ways_to_get_rfcs
> >
> > Requests for special distribution should be addressed to either the
> > author of the RFC in question, or to RFC-Manager@RFC-EDITOR.ORG.  Unless
> > specifically noted otherwise on the RFC itself, all RFCs are for
> > unlimited distribution.echo
> > Submissions for Requests for Comments should be sent to
> > RFC-EDITOR@RFC-EDITOR.ORG.  Please consult RFC 2223, Instructions to RFC
> > Authors, for further information.
> >
> >
> > Joyce K. Reynolds and Sandy Ginoza
> > USC/Information Sciences Institute
> >
>
> --
> Mark Nottingham
> http://www.mnot.net/
>
>

___________________________________________________________________
S. Alexander Jacobson                   i2x Media
1-212-787-1914 voice                    1-603-288-1280 fax
Received on Thursday, 14 February 2002 15:21:52 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Monday, 7 December 2009 10:59:06 GMT