[
Lists Home |
Date Index |
Thread Index
]
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
/ John Cowan <jcowan@reutershealth.com> was heard to say:
| Norman Walsh scripsit:
|
|> What if the GET drops a can of coke on your desk?
|
| Short of matter replication (Star Trek or Drexler varieties), it can't do
| that.
I suppose that depends how literally you interpret my words. Anyway,
suppose that the coke machine is in my office and there's a chute from
the machine to my desk. I do a GET and it drops the can which rolls
onto my desk. That at least takes the transporter out of the picture.
| If the can is brought from somewhere else, that's a side effect,
| and GETs have to be idempotent and therefore side-effect-free.
Well, strictly they don't have to be side-effect free.
RFC 2068 reads:
> Naturally, it is not possible to ensure that the server does not
> generate side-effects as a result of performing a GET request; in
> fact, some dynamic resources consider that a feature. The important
> distinction here is that the user did not request the side-effects,
> so therefore cannot be held accountable for them.
I read that as certainly saying I can't be charged for the coke if I
use a GET to deliver it. But if the coke is free...
In any event, I'll concede that I am requesting the side-effect and
really shouldn't be using GET.
My point, if I have one, is that I don't see a clear and easy
distinction between URIs that identify physical things and URIs that
identify "information resources". At a distance, it's not clear to me
that you can tell which is which and that suggests that the
distinction isn't real.
Be seeing you,
norm
- --
Norman Walsh <ndw@nwalsh.com> | The things we have most longed for do
http://nwalsh.com/ | not happen; or if they do, it is never
| at the time nor under the circumstances
| when they could have made us
| happiest.--La Bruyère
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.2 (GNU/Linux)
Comment: Processed by Mailcrypt 3.5.7 <http://mailcrypt.sourceforge.net/>
iD8DBQE/KTiHOyltUcwYWjsRAvyXAJ0RXLRLMXtXGtoLPjL9E1wO7k9d2ACdEY1Q
d1Mr9ytpmLoSOCdX0e9dkLk=
=SqA9
-----END PGP SIGNATURE-----
|
