Re: [rest-discuss] Re: GoogleAPI is Rest?
- On Wed, May 01, 2002 at 10:52:37PM +0100, Bill de hÓra wrote:
> Maybe they're not exclusive, I'm not sure. A (network) protocol isBut that's the rub. The Web *is* your application. Or more precisely,
> interesting insofar as it's a useful abstraction (of the network).
> Having to think about SOAP and JMS, or SOAP and HTTP or SOAP and BEEP,
> means I can't just think my application and SOAP,
to use the Web, you have to form your application in the shape of the
Mark Baker, Chief Science Officer, Planetfred, Inc.
Ottawa, Ontario, CANADA. mbaker@...
- --- In rest-discuss@y..., Lucas Gonze <lucas@g...> wrote:
> Is there anything to accomplish via a BOF at ETCON? IE,I posted a few suggestions at
> a convincing agenda?
> I submitted a description for an ETCON BOF called "Alternative WebCare to run a BOF on any of the below? Not sure which one "Alternative
> Services Architectures". I don't think that in one or two hours we can
> make huge progress towards understanding each other but it may help to
> hash out a few issues.
> Paul Prescod
Web Services Architectures" is...
* "Standardization of Web Services"
* "Implementing REST" (a tutorial)
* "Choosing the Right Web Services Design for your
Question: what issues need to be covered in a tutorial?
* gross overgeneralizations taken from The Thesis
* something about URIs
Is there anything to say about this?
* semantic meaning of methods; PUT/POST/GET/DELETE
* resource modeling
define resource and representation
* using status codes aside from 200
* where XML fits in
SOAP as payload format rather than RPC packager
- Lucas Gonze wrote:
>FYI (not to imply that you are suggesting otherwise, but I have seen others
> * using status codes aside from 200
comment on this)
- Sam Ruby
- [mailed and posted: http://www.oreillynet.com/cs/weblog/view/cs_msg/7174%5d
I think talking about whether REST applies to long lived conversations would
be a great topic.
There has been discussion about this on the REST forums, but it would be
good to go over it again.
As for HTTP, there is a response code of '202 Accepted' which is used to
indicate that the request is being processed asynchronously - which leads to
the 'five days for a response' situation. What hasn't happened is for a
large number of people to implement a standard approach for sending that
final response message to the sender - but there are lots of ways to do that
(take a look at the REST discussion groups).
----- Original Message -----
From: "sa3ruby" <rubys@...>
Sent: Thursday, May 02, 2002 6:00 AM
Subject: [rest-discuss] Re: etcon BOF?
> --- In rest-discuss@y..., Lucas Gonze <lucas@g...> wrote:
> > Is there anything to accomplish via a BOF at ETCON? IE,
> > a convincing agenda?
> I posted a few suggestions at