Adam Rifkin wrote:
> Then again, there's no reason Napster couldn't be a Web app as long
> as everyone who plays is willing to run their own Web server. (I think
> this is a Dave Winer idea. Would it be so hard for the average citizen
> to run their own Web server? Probably, in a world of NATs and firewalls
> and paranoia about exposing one's own desktop.)
The problem with just a Web server is that you would want
writable data, download management, dynamic naming, and a better
view into user's folders. This is the same web publishing
problem from long ago. Why do users have to download mp3's
using a browser and have to update their mp3's using FTP or
the local file system? How do they sync their music repositories
or smaller playlists between their home, work, laptop, iPAQ,
Uproar, and car radio?
Also, there's this whole DAV versus SOAP thing going on in the
world.
For a DAV copy request...(courtesy of Art Hitomi)
COPY /container/ HTTP/1.1
Host: www.foo.bar
Destination:http://www.foo.bar/othercontainer/
Depth: infinity Content-Type: text/xml; charset="utf-8“
Content-Length: xxxx
<?xml version="1.0" encoding="utf-8" ?>
<d:propertybehavior xmlns:d="DAV:">
<d:keepalive>*</d:keepalive>
</d:propertybehavior>
DAV copy response...
HTTP/1.1 207 Multi-Status
SOAP request....(yes, character hardlines and formatting
POST /Container/ HTTP/1.1 Host: www.stockquoteserver.com Content-Type: text/xml;
SOAP response....
HTTP/1.1 200 OK Content-Type: text/xml; charset="utf-8" Content-Length:
Now, even with a little cleanup and formatting, what is the attraction
o It's difficult to query remote methods and services
One of the reasons I've heard why SOAP is so popular is because
You've essentially moved who has to deal with what from an extremely
So, are we going back to a day where my glue is better
>
Evne better, a Google that every time any of the information changes,
Greg
[1] http://msdn.microsoft.com/workshop/xml/articles/xmlmanifesto.asp
>
This archive was generated by hypermail 2b29
: Fri Apr 27 2001 - 23:14:48 PDT
Content-Type: text/xml; charset="utf-8"
Content-Length: xxxx
<?xml version="1.0" encoding="utf-8" ?>
<d:multistatus xmlns:d="DAV:">
<d:response>
<d:href>http://www.foo.bar/othercontainer/R2/>
<d:status>HTTP/1.1 412 Precondition Failed</d:status>
</d:response>
</d:multistatus>
courtesy of MSFT and preserved for posterity).
charset="utf-8" Content-Length: nnnn SOAPAction:
"Some-URI" <SOAP-ENV:Envelope xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/" SOAP-ENV:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/"> <SOAP-ENV:Body> <m:Copy
xmlns:m="Some-URI"> <destination>http://www.foo.bar/othercontainer/
</destination> </m:Copy> </SOAP-ENV:Body> </SOAP-ENV:Envelope>
nnnn <SOAP-ENV:Envelope xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/" SOAP-ENV:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/"/> <SOAP-ENV:Body> <m:Status
xmlns:m="Some-URI"> <Response-Code>200</Response-Code> </m:Status> </SOAP-ENV:Body> </SOAP-ENV:Envelope>
of SOAP? What is it that you can do with SOAP that you can't do with a more
well-formed separation of concerns that DAV offers? Lets see, in SOAP, it
requires common logic, APIs, and technology including a sometimes language
specific binding on both sides of the wire, and:
o You have to parse envelopes
o It moves the logic from the protocol to the implementation
of XML-RPC and HTTP-based remote procedure calls. How hard is
it to take an XDR buffer and POST, PUT, GET, COPY, MOVE, HEAD, or
anything else to it?
flexible consensus of HTTP extensions agreed upon by a couple
of dozen companies right back to interoperability is only achievable
a priori.
than your glue? If this is Winer's world, thank gawd I don't
have to live in it. Is this all we have to look forward to? [1]
> In a world where everyone runs their own Web server, searching basically
> amounts to Googling.
it automatically gets indexed and pushed off to Google in their
own internal cache format.
> ----
> Adam@KnowNow.Com
>
> P2P is simply another step in the evolution of the internet, not the
> terrific buzz-worthy quantum leap that it's been hyped. This doesn't
> mean it's not interesting -- the opportunities made feasible when every
> computer is a server are potentially thrilling -- it just doesn't feel
> like the New New Thing.
> -- http://www.peterme.com/ March 18, 2001
--
Gregory Alan Bolcer | gbolcer@endtech.com | work: 949.833.2800
Chief Technology Officer | http://www.endtech.com | cell: 714.928.5476
Endeavors Technology, Inc. | efax: 603.994.0516 | wap: 949.278.2805