Lists Home |
Date Index |
- To: "Alaric Snell" <firstname.lastname@example.org>,<email@example.com>
- Subject: RE: [xml-dev] MS thinks HTTP Needs Replacing???
- From: "Dare Obasanjo" <firstname.lastname@example.org>
- Date: Wed, 27 Feb 2002 12:27:43 -0800
- Thread-index: AcG/grPS7FJrzCPNSNOgt7eleg1UIQASX8UQ
- Thread-topic: [xml-dev] MS thinks HTTP Needs Replacing???
> -----Original Message-----
> From: Alaric Snell [mailto:email@example.com]
> Sent: Wednesday, February 27, 2002 3:30 AM
> To: firstname.lastname@example.org
> Subject: Re: [xml-dev] MS thinks HTTP Needs Replacing???
> The one thing that HTTP has and most RPC protocols lack is
> that there is a
> way of flagging a request as being cacheable (making it a
> GET), and it's not
> even that well done in HTTP.
> I'm designing an RPC protocol that has better caching than
> HTTP. Service
> providers can even 'prefill' the cache by filling a table
> with what most
> people would call 'static content', which the underlying server
> implementation might use to broadcast out information by satellite to
> worldwide caches, Akamai-style...
This is one of the things that interested me about REST when I read
Fieldings dissertation and Paul Prescod's criticisms of SOAP. If web
services are going to become as ubiqituous as some of us would like then
there should be some way to build scalability into the system similar to
how has been done on the web with HTTP.
I'd be very interested at taking a look at your protocol if you ever
wrote it up and made it available online.
THINGS TO DO IF I BECOME AN EVIL OVERLORD #52
I will hire a team of board-certified architects and surveyors to
my castle and inform me of any secret passages and abandoned tunnels
I might not know about.