From: "Mike Dierken" <mdierken@...>
>
> From: "Seairth Jacobs" <seairth@...>
>
> > I've been continuing to give this some thought. At this point, I'm
still
> > not sure whether notifications should have URIs. For instance, in HTTP,
> we
> > think nothing of pulling a representation of a resource. But what about
> > pushing a representation of a resource?
> Isn't that what PUT does?

That's not what I mean. Suppose the notification has an associated URI like
http://seairth.com/rna/234. Now, what I want to do is push a representation
of that resource to a recipient server. I am not creating a new resource on
the recipient server, just pushing a representation of my own resource. I
think that POST would be used here. 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?".

---
Seairth Jacobs
seairth@...