OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.

 


Help: OASIS Mailing Lists Help | MarkMail Help

 


 

   RE: [xml-dev] Generality of HTTP

[ Lists Home | Date Index | Thread Index ]

*Just* for comparison's sake, what methods do the 
other protocols (UDP, ftp, etc) have and why? 

One of our developers looking at HTTP and UDP 
said, "But sometimes we need to push the data 
to lots of different places and that isn't 
HTTP!"  BTW:  reliability is not simply 
about delivering packets but sometimes 
about getting them there on time, so what 
Al was saying is relevant if it affects the 
ability of the push dispatch to get the 
right messages to the right places on time. 
VRML multicasting struggled with this mightily. 
How many real-time 3D gamers use HTTP, or the 
DIS simulations?  Are they "off the web"?  
They don't think so.

There ain't no The Web.  Just a bunch of 
pieces hooked up and variously reliable 
each according to their owner's intentions 
... Just As God Intended. :-)

len

From: Mark Baker [mailto:distobj@acm.org]

> There isn't a whole there; just pieces to wire up 
> into various systems with varying degrees of 
> interoperation depending on the way these are 
> hooked together,

And that's "just"?! 8-O

Dave wrote (if I've got the attributions correct);
> Fascinating question.  Is the web identified by protocols, formats,
> identifiers, or some combination?  Is the web:
> 
> 1) HTML, URLs, HTTP?
> 2) XML and HTML, URLs, HTTP
> 3) XML, URLs, HTTP
> 4) XML, URIs
> 5) XML and HTML, URIs
> 6) URIs
> 
> or some other combinations?
> 
> I tend to personally think the web is #5 and it typically uses HTTP.

There was a Web before XML.  I'd say it's closer to #1.  URIs are the
core, of course.  But running a close second is HTTP, or more precisely
the architectural style that it embodies (aka REST).  HTTP may be
replaced in time (no time soon though, and not by SOAP - and we won't
need a new URI scheme either), but whatever that new protocol is, it
will look an awful lot like HTTP and will at least have the same basic
methods; GET, PUT, POST, DELETE.  

As Gavin said, the Web is an *application*.  Applications need
application semantics, and HTTP provides them.

> If I build an RDF application using URIs and I use gnutella/tcp to
> distribute it, is it part of the web?
> If I build a SOAP document and ship it via SMTP, is it part of the web?

Don't want to go there, except to say if the SOAP document is an RPC
call, it's definitely not the Web.




 

News | XML in Industry | Calendar | XML Registry
Marketplace | Resources | MyXML.org | Sponsors | Privacy Statement

Copyright 2001 XML.org. This site is hosted by OASIS