RE: Binding

Miles,

Excellent.  I'd tried to do the same earlier as well.  There's a little bit
more to do to finish this off.

The last little bit is to realize that the "late binding" in the web is the
human user.  The server developer will have to know to associate the URI
with a particular text string (IBM in this case), and then the human user
will have to click on the link.  You could probably substitute "A human
figures out" wherever the string "No A priori knowledge" appears in most
cases.  The other substitution string would be "The browser programmer who's
read and programmed to 2396 and 2616".

The web works because humans do the late binding, kind of like
"post-priori".  Programs can't do that, yet.  .

Cheers,
Dave

> -----Original Message-----
> From: www-ws-arch-request@w3.org [mailto:www-ws-arch-request@w3.org]On
> Behalf Of Miles Sabin
> Sent: Monday, January 06, 2003 8:07 AM
> To: www-ws-arch@w3.org
> 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
>
>

Received on Monday, 6 January 2003 15:01:43 UTC