----- Original Message -----
From: "Seairth Jacobs" <seairth@...>

> However, the recipient doesn't really
> have a way to *know* that the POSTed representation belongs to the
resource
> at http://seairth.com/rna/234 unless the recipient turns around and GETs
the
> representation from that URI. So then we are back to the question of "why
> push a representation?".
How about associating Authentication information in the POST request with
the authority of the indicated URI - meaning use something that verifies the
request as coming from search.com.
The assumption being that the host controls all URI within it.