RE: Binding

Pardon my ignorance, I am wondering what a RESTfull or RESTLess business
transaction would look like (not getastockquote). 

I have a suggestion, now that Office is XML enabled, we could all return
to using GOFM (good old fax machines), and fax our XML back and forth.
That way you get security, non-repudiation and guaranteed delivery for
free, things that are far from given when you use an HTTP GET/POST with
SOAP bubbles or not.

Jean-Jacques Dubray____________________

PS: I have been working with web services since 1998 (remember
BowStreet?) and since 1998 the only meaningful example people can come
up with is getting a stock quote and make generalizations from it. This
is so depressing.
 

>>-----Original Message-----
>>From: [email protected] [mailto:[email protected]]
On
>>Behalf Of Miles Sabin
>>Sent: Monday, January 06, 2003 11:07 AM
>>To: [email protected]
>>Subject: Re: Binding
>>
>>
>>Mark Baker wrote,
>>> On Mon, Jan 06, 2003 at 03:23:15PM +0000, Miles Sabin wrote:
>>> > I'd like you to explain _in_detail_ why these two conditions are
>>> > less demanding than the corresponding conditions for (2').
>>>
>>> Ok, here goes ...
>>>
>>> Here's what a RESTful client needs to know in order to get the data;
>>>
>>> - URI
>>> - HTTP GET
>>>
>>> Here's what a Web services client needs to know in order to get the
>>> data;
>>>
>>> - URI
>>> - what "getLastSharePriceOfIBM" means
>>
>>Frankly, this is just smoke and mirrors.
>>
>>The URI in the REST case contains the substring "/ibm/lastshareprice".
>>It needs to know what that substring means just as much (or as little)
>>as the RESTless client needs to know what "getLastSharePriceOfIBM"
>>means.
>>
>>Getting rid of a priori knowledge isn't as easy as string
concatenation.
>>
>>Is this really the best you can do? If it is, then I spy a naked
>>emperor.
>>
>>Cheers,
>>
>>
>>Miles